@spark-web/text-link
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@spark-web/a11y | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages that may re-export rather than directly import. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.4.0 | 8 / 2 | |
| 5.3.3 | 8 / 2 | |
| 5.3.2 | 8 / 2 | |
| 5.3.0 | 8 / 2 | |
| 5.2.0 | 8 / 2 | |
| 5.1.0 | 8 / 2 | |
| 5.0.1 | 8 / 2 | |
| 5.0.0 | 8 / 2 |
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.