Verify

​

What it does

​

Usage

filepacks verify <file>

​

When to use it

• before treating an artifact as evidence
• before comparing against another artifact
• when you suspect corruption or malformed input
• when you received the artifact from somewhere else

​

What verify checks

• archive structure
• manifest validity
• expected payload paths
• file sizes
• file hashes
• the aggregate payload_digest

​

Minimal example

npx filepacks verify ./artifact.fpk

​

Expected output shape

Verify
path=/absolute/path/to/artifact.fpk
ok=true
files_checked=2

Verify
path=/absolute/path/to/artifact.fpk
ok=false
error=hash_mismatch:Hash mismatch for: summary.txt

​

Exit behavior

• exit 0: artifact is valid
• exit 1: artifact is invalid or the command was used incorrectly

​

Common mismatch codes

• archive_malformed
• digest_mismatch
• hash_mismatch
• manifest_invalid
• missing_payload_file
• size_mismatch
• unexpected_payload_file

​

Common mistakes

• skipping verify and assuming inspect is enough
• treating ok=false as a semantic judgment instead of an integrity failure
• comparing against an artifact that has never been verified

​

Related commands

• inspect for a quick summary
• compare after integrity has been confirmed
• pack to recreate a trusted artifact from the original directory

​

Core API

const result = await verify({artifact: '/tmp/example.fpk'})

if (!result.ok) {
  console.log(result.mismatches)
}