@cedarjs/prerender
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:babel-plugin-ignore-html-and-css-imports | AI (dependencies): Small, purpose-specific Babel plugin appropriate for a prerender package; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established CedarJS monorepo package; provenance absence is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:@swc/core | AI (phantom-deps): @swc/core is a direct dependency used via rollup-plugin-swc3; phantom-dep is a false positive here. | ai | |
| phantom-deps | phantom-dep:babel-plugin-ignore-html-and-css-imports | AI (phantom-deps): Referenced in build config files; legitimate dependency for this prerender package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README is typical for internal monorepo packages; not indicative of spam or malice. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 5.0.4 | 23 / 10 | |
| 5.0.3 | 23 / 10 | |
| 5.0.2 | 23 / 10 | |
| 5.0.1 | 23 / 10 | |
| 5.0.0 | 23 / 10 | |
| 4.2.0 | 25 / 9 | |
| 4.1.0 | 26 / 9 | |
| 4.0.0 | 26 / 9 | |
| 3.1.1 | 26 / 9 | |
| 3.1.0 | 26 / 9 | |
| 3.0.0 | 26 / 9 | |
| 2.8.1 | 26 / 9 | |
| 2.8.0 | 26 / 9 | |
| 2.7.0 | 26 / 9 | |
| 2.6.0 | 26 / 9 | |
| 2.5.1 | 26 / 9 | |
| 2.5.0 | 26 / 9 | |
| 2.4.1 | 26 / 9 | |
| 2.4.0 | 26 / 9 | |
| 2.3.0 | 26 / 9 | |
| 2.2.1 | 26 / 9 | |
| 2.2.0 | 26 / 9 | |
| 2.1.1 | 26 / 9 | |
| 2.1.0 | 26 / 9 | |
| 2.0.3 | 26 / 9 | |
| 2.0.2 | 26 / 9 | |
| 2.0.1 | 26 / 9 | |
| 2.0.0 | 26 / 9 | |
| 1.1.2 | 26 / 9 | |
| 1.1.1 | 26 / 9 | |
| 1.1.0 | 26 / 9 | |
| 1.0.0 | 26 / 9 |
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.