@ssa-ui-kit/templates
SSA UI Kit templates
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/809.index.js | AI (source-diff): Standard webpack bundle output; content is identifiable Firebase/idb code, not obfuscation. | ai | |
| dependencies | unvetted-dep:@nivo/line | AI (dependencies): @nivo/line is a well-known charting library; its use is consistent with this UI kit's charting features across versions. | ai | |
| provenance | no-provenance | AI (provenance): Internal UI kit package; no provenance attestation is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:loose-envify | AI (phantom-deps): Build-time env transform dep; not directly imported in source. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Declared for build/config use; not a runtime import concern for this UI kit package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/react | AI (phantom-deps): UI positioning dep used transitively; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:plotly.js | AI (phantom-deps): Bundled dependency used indirectly via react-plotly.js; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@nivo/line | AI (phantom-deps): Charting dep likely re-exported or used in compiled output; stable false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.11.0 | 15 / 13 | |
| 3.10.5 | 15 / 13 | |
| 3.10.2 | 15 / 13 | |
| 3.9.0 | 15 / 13 | |
| 3.8.0 | 15 / 13 | |
| 3.7.0 | 15 / 13 | |
| 3.6.0 | 15 / 13 | |
| 3.5.0 | 15 / 13 | |
| 3.4.0 | 15 / 13 | |
| 3.2.0 | 15 / 13 | |
| 3.1.0 | 15 / 13 | |
| 3.0.0 | 15 / 13 | |
| 2.33.0 | 15 / 12 | |
| 2.32.0 | 15 / 12 | |
| 2.31.0 | 15 / 12 | |
| 2.29.0 | 15 / 12 |
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.