riot
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:got | AI (typosquat): riot is a 12-year-old UI framework with no relation to 'got'; Levenshtein match is coincidental. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is used in riot+compiler.cjs to evaluate compiled component code; expected behavior for a template compiler. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 10.1.4 | 1 / 33 | |
| 10.1.3 | 1 / 33 | |
| 10.1.2 | 1 / 33 | |
| 10.1.1 | 1 / 33 | |
| 10.1.0 | 1 / 33 | |
| 10.0.1 | 1 / 33 | |
| 10.0.0 | 1 / 33 |
v10.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.