@colbymchenry/codegraph
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@clack/prompts | AI (phantom-deps): CLI prompt library used indirectly, benign. | ai | |
| phantom-deps | phantom-dep:sisteransi | AI (phantom-deps): Transitive prompt-lib dep, referenced via config not direct import. | ai | |
| phantom-deps | phantom-dep:fast-string-width | AI (phantom-deps): Utility dep referenced via config, benign. | ai | |
| phantom-deps | phantom-dep:fast-wrap-ansi | AI (phantom-deps): Utility dep referenced via config, benign. | ai | |
| phantom-deps | phantom-dep:tree-sitter-wasms | AI (phantom-deps): Platform WASM binary loaded at runtime, not statically imported; stable FP. | ai | |
| phantom-deps | phantom-dep:tree-sitter-liquid | AI (phantom-deps): Used via config/query files, not direct import; expected for tree-sitter grammars. | ai | |
| dependencies | unvetted-dep:tree-sitter-liquid | AI (dependencies): Grammar dep matches package's multi-language parsing purpose. | ai | |
| npm-metadata | url-dep:tree-sitter-liquid | AI (npm-metadata): GitHub dep is a niche unpublished grammar, consistent with tree-sitter ecosystem. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall patches tree-sitter native bindings; stable for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Platform-specific binary resolution pattern, standard for optionalDependencies-based native packages. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Shim invokes resolved platform binary; expected for this package's architecture. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 0 / 0 | |
| 1.4.1 | 0 / 0 | |
| 1.4.0 | 0 / 0 | |
| 1.3.1 | 0 / 0 | |
| 1.3.0 | 0 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.6 | 0 / 0 | |
| 1.1.5 | 0 / 0 | |
| 1.1.4 | 0 / 0 | |
| 1.1.3 | 0 / 0 | |
| 1.1.2 | 0 / 0 | |
| 1.1.1 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 | |
| 0.9.9 | 0 / 0 | |
| 0.9.8 | 0 / 0 | |
| 0.9.7 | 0 / 0 | |
| 0.9.6 | 0 / 0 | |
| 0.9.5 | 0 / 0 | |
| 0.9.4 | 0 / 0 | |
| 0.9.3 | 0 / 0 | |
| 0.9.2 | 0 / 0 | |
| 0.9.1 | 0 / 0 | |
| 0.9.0 | 0 / 0 | |
| 0.8.0 | 10 / 5 | |
| 0.7.10 | 10 / 5 | |
| 0.7.9 | 10 / 5 | |
| 0.7.4 | 9 / 5 | |
| 0.7.3 | 6 / 5 | |
| 0.7.2 | 6 / 5 | |
| 0.6.5 | 7 / 6 | |
| 0.6.2 | 7 / 6 | |
| 0.5.7 | 7 / 6 | |
| 0.5.5 | 7 / 6 | |
| 0.5.3 | 6 / 6 | |
| 0.5.0 | 6 / 6 | |
| 0.2.9 | 20 / 5 |
v1.5.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (colbymchenry) on 2026-07-21, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.