Code format

PS1 Sample Files

PowerShell (.ps1) files contain task automation scripts for Windows and cross-platform PowerShell runtimes. Use sample PS1 files to test parser support, policy enforcement, and command-audit workflows.

4 files All to 1MB SHA256 verified Manifest included
Quick facts
CategoryCode
Total Files4
Extension.ps1
MIMEapplication/octet-stream
ManifestJSON
Request Related Coverage
Files first

Start with one representative file.

Starter file

ps1_sample_file_1MB.ps1 · 1.0 MB

Download
Filename Size MIME Download
.ps1 Starter SHA256 db9881885ee3...
1.0 MB application/octet-stream Download
.ps1 Realistic SHA256 faef9280ba49...
200.0 KB application/octet-stream Download
.ps1 SHA256 e5e527d9b527...
500.0 KB application/octet-stream Download
.ps1 SHA256 a6560026a6ff...
50.0 KB application/octet-stream Download
Use cases

Pick the next task, not just the next file.

Use the file table first, then branch into compare or FAQ only if the task needs more context.

Compare and decide

Keep the next decision one step away.

PowerShell vs Shell Scripts

Compare Windows PowerShell scripts and POSIX shell scripts for automation tasks.

Open Comparison
FAQ and reference

Keep the operational details quiet.

Checksum Verification

Use checksums to confirm file integrity after download.

shasum -a 256 your_file_name_here
# Compare output with SHA256 values listed above.
Where is the machine-readable manifest?

Use the manifest when you need stable names, SHA256 values, and URLs for automation.

Validation Methodology
  • Validate syntax-highlight pipelines and file-type detection.
  • Test parser robustness for larger source samples.
  • Confirm linting/formatting tools handle encoding correctly.