@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, so a manually published version cannot be tied back to a reviewed commit.
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/jaemin-BG8HRXG1.cjs | AI (source-diff): Vite build output (minified CJS); DOM animation code matching package purpose, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/multi-animation-uzEnQnrG.cjs | AI (source-diff): Standard Vite/esbuild minified build output; spring-physics animation code with no malicious behavior. | ai | |
| source-diff | obfuscated-file:dist/multi-animation-qtH1IKNG.cjs | AI (source-diff): Vite/Rollup minified build output; spring-physics animation logic is readable, no true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/internal.cjs | AI (source-diff): Vite/Rollup minified build output; animation logic is readable, no true obfuscation. | ai | |
| publish-pattern | suspicious-version-number | AI (publish-pattern): 6.6.6 is a legitimate semver for this package; no malicious behavior found. | ai | |
| 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 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 6.6.6 | 0 / 10 | |
| 6.6.1 | 0 / 10 | |
| 6.5.1 | 0 / 10 | |
| 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 | |
| 4.3.0 | 0 / 10 | |
| 3.4.0 | 0 / 10 | |
| 3.2.0 | 0 / 10 | |
| 3.1.4 | 0 / 10 | |
| 3.1.2 | 0 / 10 | |
| 3.1.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 |
v6.6.6
4 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.
Newly 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.
v4.3.0
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.