@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, so a manually published version cannot be tied back to a reviewed commit.
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 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 5.7.0 | 10 / 2 | |
| 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 | |
| 5.3.3 | 10 / 2 | |
| 5.3.2 | 10 / 2 | |
| 5.3.1 | 10 / 2 | |
| 5.3.0 | 10 / 2 | |
| 5.2.1 | 10 / 2 | |
| 5.2.0 | 10 / 2 | |
| 5.1.0 | 10 / 2 | |
| 5.0.3 | 10 / 2 | |
| 5.0.2 | 10 / 2 | |
| 5.0.1 | 10 / 2 | |
| 5.0.0 | 10 / 2 |
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.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.