@spark-web/button
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@spark-web/icon | AI (dependencies): Same-monorepo sibling package from trusted brighte-labs publisher; stable false positive. | ai | |
| dependencies | unvetted-dep:@spark-web/link | AI (dependencies): Same-monorepo sibling package from trusted brighte-labs publisher; stable false positive. | ai | |
| dependencies | unvetted-dep:@spark-web/spinner | AI (dependencies): Same-monorepo sibling package from trusted brighte-labs publisher; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Established package from known org; lack of provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.6.1 | 10 / 2 | |
| 5.6.0 | 10 / 2 | |
| 5.5.3 | 10 / 2 | |
| 5.5.2 | 10 / 2 | |
| 5.5.0 | 10 / 2 | |
| 5.4.0 | 10 / 2 |
v5.6.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (brighte) than the most recent previously approved version (brighte-release-bot) on 2026-01-15, but brighte is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.