@contrast/architecture-components
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@contrast/logger | AI (phantom-deps): Same-org monorepo dep; not directly imported but re-exported via package structure. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@contrast/patcher | AI (phantom-deps): Same-org monorepo dep; not directly imported but re-exported via package structure. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@contrast/dep-hooks | AI (phantom-deps): Same-org monorepo dep; not directly imported but re-exported via package structure. Stable FP for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.49.0 | 4 / 0 | |
| 1.48.1 | 4 / 0 | |
| 1.48.0 | 4 / 0 | |
| 1.47.1 | 4 / 0 | |
| 1.47.0 | 4 / 0 | |
| 1.46.0 | 4 / 0 | |
| 1.45.1 | 4 / 0 | |
| 1.45.0 | 4 / 0 | |
| 1.44.0 | 4 / 0 | |
| 1.43.0 | 4 / 0 | |
| 1.42.2 | 4 / 0 | |
| 1.42.1 | 4 / 0 | |
| 1.42.0 | 4 / 0 | |
| 1.41.0 | 4 / 0 | |
| 1.40.0 | 4 / 0 | |
| 1.39.0 | 4 / 0 |
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.