@contrast/agentify
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Template literal loads known sibling validator modules by spec name; not user-controlled arbitrary input. | ai | |
| phantom-deps | phantom-dep:@contrast/metrics | AI (phantom-deps): Same-org dependency; likely consumed transitively within the Contrast agent monorepo. | ai | |
| phantom-deps | phantom-dep:@contrast/sources | AI (phantom-deps): Same-org dependency; likely consumed transitively within the Contrast agent monorepo. | ai | |
| phantom-deps | phantom-dep:@contrast/instrumentation | AI (phantom-deps): Same-org dependency; likely consumed transitively within the Contrast agent monorepo. | ai | |
| phantom-deps | phantom-dep:on-finished | AI (phantom-deps): Declared dependency used in config/middleware context; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal enterprise security agent component; sparse public metadata is expected for this package type. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.67.1 | 20 / 0 | |
| 1.67.0 | 20 / 0 | |
| 1.66.1 | 20 / 0 | |
| 1.66.0 | 20 / 0 | |
| 1.65.1 | 20 / 0 | |
| 1.65.0 | 20 / 0 | |
| 1.64.1 | 20 / 0 | |
| 1.64.0 | 20 / 0 | |
| 1.63.1 | 20 / 0 | |
| 1.63.0 | 20 / 0 | |
| 1.62.0 | 20 / 0 | |
| 1.61.1 | 19 / 0 | |
| 1.61.0 | 19 / 0 | |
| 1.60.0 | 18 / 0 | |
| 1.59.1 | 18 / 0 | |
| 1.59.0 | 18 / 0 | |
| 1.58.0 | 18 / 0 | |
| 1.57.0 | 18 / 0 | |
| 1.56.0 | 18 / 0 | |
| 1.55.0 | 18 / 0 | |
| 1.54.0 | 18 / 0 | |
| 1.53.0 | 18 / 0 | |
| 1.52.2 | 17 / 0 | |
| 1.52.1 | 17 / 0 | |
| 1.52.0 | 17 / 0 | |
| 1.51.0 | 17 / 0 | |
| 1.50.0 | 17 / 0 | |
| 1.49.0 | 17 / 0 | |
| 1.48.0 | 17 / 0 |
v1.67.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.