newskit
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
newskit
Keywords
reactnewsuk
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; lack of provenance is common and not a risk signal here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is a webpack lazy-load pattern in theme-checker; path is constructed from known component names, not user input. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a well-known polyfill runtime dependency; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/minimatch | AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package. | ai |
v9.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.