@certd/plugin-cert
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): rimraf is listed as a runtime dependency in package.json and used in build scripts; phantom-dep heuristic misfires here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; empty entry point and missing metadata are structural, not malicious. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all @certd monorepo packages; not a spam indicator here. | ai | |
| dependencies | unvetted-dep:@certd/plugin-lib | AI (dependencies): Same-monorepo sibling dependency at matching version; not an external unvetted package. | ai |
Versions (showing 100 of 212)
| Version | Deps | Published |
|---|---|---|
| 1.34.7 | 11 / 13 | |
| 1.34.6 | 11 / 13 | |
| 1.34.5 | 11 / 13 | |
| 1.34.4 | 11 / 13 | |
| 1.34.3 | 11 / 13 | |
| 1.34.2 | 11 / 13 | |
| 1.34.1 | 11 / 13 | |
| 1.34.0 | 11 / 13 | |
| 1.33.8 | 11 / 13 | |
| 1.33.7 | 10 / 13 | |
| 1.33.6 | 10 / 13 | |
| 1.33.5 | 10 / 13 | |
| 1.33.4 | 10 / 13 | |
| 1.33.3 | 10 / 13 | |
| 1.33.2 | 10 / 13 | |
| 1.33.1 | 10 / 13 | |
| 1.33.0 | 10 / 13 | |
| 1.32.0 | 10 / 13 | |
| 1.31.11 | 10 / 13 | |
| 1.31.10 | 10 / 13 | |
| 1.31.9 | 10 / 13 | |
| 1.31.8 | 10 / 13 | |
| 1.31.7 | 10 / 13 | |
| 1.31.6 | 10 / 13 | |
| 1.31.5 | 10 / 13 | |
| 1.31.4 | 10 / 13 | |
| 1.31.3 | 10 / 13 | |
| 1.31.2 | 10 / 13 | |
| 1.31.1 | 10 / 13 | |
| 1.31.0 | 10 / 13 | |
| 1.30.6 | 10 / 13 | |
| 1.30.5 | 10 / 13 | |
| 1.30.3 | 10 / 13 | |
| 1.30.2 | 10 / 13 | |
| 1.30.1 | 10 / 13 | |
| 1.30.0 | 10 / 13 | |
| 1.29.5 | 10 / 13 | |
| 1.29.4 | 10 / 13 | |
| 1.29.3 | 10 / 13 | |
| 1.29.2 | 9 / 13 | |
| 1.29.1 | 9 / 13 | |
| 1.29.0 | 9 / 13 | |
| 1.28.4 | 9 / 13 | |
| 1.28.3 | 9 / 13 | |
| 1.28.2 | 9 / 13 | |
| 1.28.1 | 9 / 13 | |
| 1.28.0 | 9 / 13 | |
| 1.27.9 | 9 / 13 | |
| 1.27.8 | 9 / 13 | |
| 1.27.7 | 9 / 13 | |
| 1.27.6 | 9 / 13 | |
| 1.27.5 | 9 / 13 | |
| 1.27.4 | 9 / 13 | |
| 1.27.3 | 9 / 13 | |
| 1.27.2 | 9 / 13 | |
| 1.27.1 | 9 / 30 | |
| 1.27.0 | 9 / 30 | |
| 1.26.16 | 9 / 30 | |
| 1.26.15 | 9 / 30 | |
| 1.26.14 | 9 / 30 | |
| 1.26.13 | 9 / 30 | |
| 1.26.12 | 9 / 30 | |
| 1.26.11 | 9 / 30 | |
| 1.26.10 | 9 / 30 | |
| 1.26.9 | 9 / 30 | |
| 1.26.8 | 9 / 30 | |
| 1.26.7 | 9 / 30 | |
| 1.26.6 | 9 / 30 | |
| 1.26.4 | 9 / 30 | |
| 1.26.3 | 9 / 30 | |
| 1.26.2 | 9 / 30 | |
| 1.26.1 | 9 / 30 | |
| 1.26.0 | 9 / 30 | |
| 1.25.9 | 7 / 31 | |
| 1.25.8 | 7 / 31 | |
| 1.25.7 | 7 / 31 | |
| 1.25.6 | 6 / 32 | |
| 1.25.5 | 6 / 32 | |
| 1.25.4 | 5 / 32 | |
| 1.25.3 | 5 / 32 | |
| 1.25.2 | 5 / 32 | |
| 1.25.1 | 5 / 32 | |
| 1.24.4 | 5 / 32 | |
| 1.24.3 | 5 / 32 | |
| 1.24.2 | 5 / 32 | |
| 1.24.1 | 5 / 32 | |
| 1.24.0 | 5 / 32 | |
| 1.23.1 | 5 / 32 | |
| 1.22.8 | 5 / 32 | |
| 1.22.7 | 5 / 32 | |
| 1.22.6 | 5 / 32 | |
| 1.22.5 | 5 / 32 | |
| 1.22.4 | 5 / 32 | |
| 1.22.3 | 5 / 32 | |
| 1.22.2 | 5 / 32 | |
| 1.22.1 | 5 / 32 | |
| 1.22.0 | 5 / 32 | |
| 1.21.2 | 5 / 33 | |
| 1.21.1 | 5 / 33 | |
| 1.21.0 | 5 / 33 |
v1.33.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.