@spark-web/action-dropdown
A pill-shaped button component that displays a dropdown menu of actions when clicked.
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 (@spark-web); consistent internal dependency across the spark-web package family. | ai | |
| phantom-deps | phantom-dep:@spark-web/box | AI (phantom-deps): Monorepo sibling; declared as dep but may be re-exported rather than directly imported — stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of Sigstore provenance is consistent across all @spark-web/* releases. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 8 / 3 | |
| 2.0.0 | 8 / 3 | |
| 1.3.2 | 8 / 3 | |
| 1.3.1 | 8 / 3 | |
| 1.3.0 | 8 / 3 | |
| 1.2.0 | 8 / 3 | |
| 1.1.0 | 8 / 3 | |
| 1.0.2 | 8 / 3 | |
| 1.0.1 | 9 / 3 |
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.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.
v1.2.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.
v1.1.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.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.