mercurius
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
matteo.collinajonnydgreen
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:borp | AI (phantom-deps): borp is a test runner listed in both devDependencies and dependencies (likely a packaging oversight), but it is not a security concern for this well-known package. | ai | |
| phantom-deps | phantom-dep:p-map | AI (phantom-deps): p-map is a legitimate declared dependency in mercurius; phantom-dep finding is a false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): mercurius is a long-established, reputable package; lack of provenance attestation is not a security concern here. | ai |
v16.10.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.
v16.9.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.8.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.