@ssgoi/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 | obfuscated-file:dist/provider-Cs5iBqRD.cjs | AI (source-diff): Vite-bundled spring physics code; minification is expected for this animation library's dist output. | ai | |
| provenance | no-provenance | AI (provenance): Established package with clean history; lack of Sigstore attestation is a process gap, not a security risk. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @ssgoi/core is a page-transition library; Levenshtein match to 'cors' is purely coincidental. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.1.0 | 0 / 10 | |
| 5.0.2 | 0 / 10 | |
| 5.0.1 | 0 / 10 | |
| 5.0.0 | 0 / 10 | |
| 4.4.1 | 0 / 10 | |
| 4.4.0 | 0 / 10 | |
| 2.5.4 | 0 / 10 | |
| 2.5.3 | 0 / 10 | |
| 2.5.2 | 0 / 10 | |
| 2.5.1 | 0 / 10 | |
| 2.5.0 | 1 / 9 |
v5.1.0
2 findingsPackage name '@ssgoi/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.
v5.0.2
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.
v4.4.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: anseotmd555.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: anseotmd555.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: anseotmd555.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.