@spark-web/nav-link
4
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
brightebrighte-release-bot
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; no provenance is the norm for this publisher. | ai | |
| dependencies | unvetted-dep:@spark-web/box | AI (dependencies): Same monorepo sibling package from brighte-labs; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@spark-web/a11y | AI (dependencies): Same monorepo sibling package from brighte-labs; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@spark-web/link | AI (dependencies): Same monorepo sibling package from brighte-labs; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@spark-web/text | AI (dependencies): Same monorepo sibling package from brighte-labs; stable false positive for this package family. | ai |
v5.0.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.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.