@ssa-ui-kit/core
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 | encoded-string-file:dist/index.js | AI (source-diff): Long hex strings are d3-scale-chromatic color palette data (viridis/magma), not obfuscated payloads; stable false positive for this UI kit bundle. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped UI kit package; name similarity to 'cors' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Build/config tool dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:plotly.js | AI (phantom-deps): Referenced in config/build files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:loose-envify | AI (phantom-deps): Build artifact dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ssa-ui-kit/hooks | AI (phantom-deps): Same-org sibling package; stable false positive for this scoped package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.12.0 | 11 / 16 | |
| 3.11.0 | 11 / 16 | |
| 3.10.5 | 11 / 16 | |
| 3.10.2 | 11 / 16 | |
| 3.9.0 | 11 / 16 | |
| 3.8.0 | 11 / 16 | |
| 3.7.0 | 11 / 16 | |
| 3.6.0 | 11 / 16 | |
| 3.5.0 | 11 / 16 | |
| 3.4.0 | 11 / 16 | |
| 3.3.0 | 11 / 16 | |
| 3.0.0 | 11 / 16 | |
| 2.33.0 | 11 / 15 | |
| 2.32.0 | 11 / 15 | |
| 2.31.0 | 11 / 15 | |
| 2.30.0 | 11 / 15 | |
| 2.29.0 | 11 / 15 |
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
2 findingsPackage name '@ssa-ui-kit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.