@spark-web/modal-dialog
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/box | AI (dependencies): Same-org monorepo sibling; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spark-web/row | AI (dependencies): Same-org monorepo sibling; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spark-web/a11y | AI (dependencies): Same-org monorepo sibling; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spark-web/icon | AI (dependencies): Same-org monorepo sibling; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spark-web/text | AI (dependencies): Same-org monorepo sibling; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spark-web/stack | AI (dependencies): Same-org monorepo sibling; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spark-web/button | AI (dependencies): Same-org monorepo sibling; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@spark-web/heading | AI (dependencies): Same-org monorepo sibling; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@spark-web/text | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 6.0.2 | 13 / 3 | |
| 6.0.1 | 13 / 3 | |
| 6.0.0 | 13 / 3 | |
| 5.2.9 | 13 / 3 | |
| 5.2.8 | 13 / 3 | |
| 5.2.7 | 13 / 3 |
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
2 findingsPackage 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.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.