@spark-web/radio
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:redis | AI (typosquat): Scoped @spark-web/radio is a UI component package; no relation to redis. False positive. | ai | |
| dependencies | unvetted-dep:@spark-web/box | AI (dependencies): Sibling package in the same @spark-web monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@spark-web/a11y | AI (dependencies): Sibling package in the same @spark-web monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@spark-web/text | AI (dependencies): Sibling package in the same @spark-web monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@spark-web/field | AI (dependencies): Sibling package in the same @spark-web monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@spark-web/stack | AI (dependencies): Sibling package in the same @spark-web monorepo; same trusted publisher. | ai | |
| dependencies | unvetted-dep:@spark-web/control-label | AI (dependencies): Sibling package in the same @spark-web monorepo; same trusted publisher. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.3.1 | 9 / 2 | |
| 5.3.0 | 10 / 2 | |
| 5.2.2 | 10 / 2 | |
| 5.2.0 | 10 / 2 | |
| 5.1.1 | 10 / 2 | |
| 5.1.0 | 10 / 2 | |
| 5.0.0 | 9 / 2 |
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.