@highstate/cert-manager
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Standard Pulumi provider SDK generation postinstall; consistent with this package's established pattern. | ai | |
| phantom-deps | phantom-dep:tmp | AI (phantom-deps): Phantom-dep heuristic; tmp is used indirectly in config/runtime. | ai | |
| phantom-deps | phantom-dep:@types/tmp | AI (phantom-deps): Type package loaded by convention; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Phantom-dep heuristic; node-fetch used indirectly in config. | ai | |
| phantom-deps | phantom-dep:@types/node-fetch | AI (phantom-deps): Type package loaded by convention; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Build/config tooling; declared for build scripts, not runtime imports. | ai | |
| phantom-deps | phantom-dep:shell-quote | AI (phantom-deps): Declared for type definitions (@types/shell-quote); runtime usage via types. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type definitions loaded by convention in TypeScript projects. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build-time dependency; TypeScript projects declare but don't import the compiler. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 6 / 3 | |
| 0.14.0 | 9 / 5 | |
| 0.13.2 | 9 / 5 | |
| 0.13.1 | 9 / 5 | |
| 0.13.0 | 9 / 5 | |
| 0.12.1 | 9 / 5 | |
| 0.12.0 | 9 / 5 | |
| 0.11.7 | 9 / 5 | |
| 0.11.6 | 9 / 5 | |
| 0.11.4 | 9 / 5 | |
| 0.10.0 | 8 / 5 | |
| 0.9.37 | 8 / 5 | |
| 0.9.36 | 8 / 5 | |
| 0.9.35 | 8 / 5 | |
| 0.9.34 | 8 / 5 | |
| 0.9.33 | 8 / 5 | |
| 0.9.32 | 8 / 5 | |
| 0.9.31 | 8 / 5 | |
| 0.9.30 | 8 / 5 | |
| 0.9.29 | 8 / 5 | |
| 0.9.28 | 8 / 5 | |
| 0.9.27 | 8 / 5 | |
| 0.9.26 | 8 / 5 | |
| 0.9.25 | 8 / 5 | |
| 0.9.24 | 8 / 5 | |
| 0.9.23 | 8 / 5 | |
| 0.9.21 | 8 / 5 | |
| 0.9.20 | 8 / 5 | |
| 0.9.19 | 8 / 5 | |
| 0.9.18 | 8 / 5 | |
| 0.9.16 | 8 / 5 | |
| 0.9.15 | 8 / 5 | |
| 0.9.14 | 8 / 5 | |
| 0.9.13 | 8 / 5 | |
| 0.9.12 | 8 / 5 | |
| 0.9.11 | 8 / 5 | |
| 0.9.10 | 8 / 5 | |
| 0.9.9 | 8 / 5 | |
| 0.9.8 | 8 / 5 | |
| 0.9.7 | 8 / 5 | |
| 0.9.6 | 8 / 5 | |
| 0.9.5 | 8 / 5 |
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: exeteres.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.21
2 findingsScript: node ./scripts/postinstall.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.20
2 findingsScript: node ./scripts/postinstall.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.19
2 findingsScript: node ./scripts/postinstall.js
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.