@contrail/document-util
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:@contrail/util | AI (phantom-deps): Same-org internal dependency; phantom-dep heuristic not applicable to monorepo patterns. | ai | |
| phantom-deps | phantom-dep:@contrail/telemetry | AI (phantom-deps): Same-org internal dependency; phantom-dep heuristic not applicable to monorepo patterns. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal utility library; sparse metadata is normal for org-scoped packages not intended for public discovery. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 1 / 9 | |
| 1.2.0 | 2 / 8 | |
| 1.1.0 | 2 / 8 | |
| 1.0.15 | 1 / 8 | |
| 1.0.14 | 1 / 8 | |
| 1.0.9 | 1 / 8 | |
| 1.0.8 | 1 / 8 | |
| 1.0.7 | 1 / 8 |
v1.2.1
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.