Skip to content

Add lockfile integrity evidence gates#1196

Open
tick25108-cpu wants to merge 1 commit into
UnitOneAI:mainfrom
tick25108-cpu:codex/dependency-lockfile-integrity
Open

Add lockfile integrity evidence gates#1196
tick25108-cpu wants to merge 1 commit into
UnitOneAI:mainfrom
tick25108-cpu:codex/dependency-lockfile-integrity

Conversation

@tick25108-cpu
Copy link
Copy Markdown

Fixes #384.

This updates the dependency-scanning skill so lockfiles are treated as artifact provenance evidence, not only as resolved dependency lists.

What changed:

  • Adds lockfile source, integrity/checksum, git immutability, install-script, signature/provenance, and manifest-lockfile alignment gates.
  • Clarifies that npm resolved, integrity, and hasInstallScript fields are normal evidence fields and should not be findings by themselves.
  • Extends the output template with artifact integrity findings and supply-chain indicators for missing integrity, unexpected artifact sources, signature gaps, and metadata drift.
  • Adds lifecycle-script safety guidance so package install hooks are reviewed as evidence, not executed.
  • Adds npm package-lock and audit-signature references.

Validation:

  • git diff --check
  • confirmed Markdown fence balance
  • confirmed markers for Lockfile Artifact Integrity, Artifact Integrity Findings, npm audit signatures, hasInstallScript, and lifecycle-script safety guidance are present

Submitting this as an Improver contribution. Payment details can be handled privately after maintainer acceptance.

@tick25108-cpu tick25108-cpu force-pushed the codex/dependency-lockfile-integrity branch from e970be2 to 0a075bd Compare June 5, 2026 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[REVIEW] dependency-scanning: add lockfile integrity and registry signature evidence

1 participant