@heejun/spa-seo-gateway-admin-ui
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:public/assets/index-CJvRfJYt.js | AI (source-diff): Standard Vite/Rolldown minified bundle for embedded React admin SPA; content is readable and consistent with package purpose. | ai | |
| source-diff | obfuscated-file:public/assets/react-vendor-ZG3n3xTH.js | AI (source-diff): Standard minified React vendor bundle produced by Vite build; content matches React internals. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by addition of bundled Vite+React frontend assets for the first time. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.10.0 | 3 / 1 | |
| 1.9.0 | 3 / 1 | |
| 1.8.1 | 3 / 1 | |
| 1.8.0 | 3 / 1 | |
| 1.7.2 | 3 / 1 | |
| 1.7.1 | 3 / 1 | |
| 1.7.0 | 3 / 1 | |
| 1.6.0 | 3 / 1 | |
| 1.5.0 | 3 / 1 | |
| 1.4.0 | 3 / 1 | |
| 1.3.0 | 3 / 1 | |
| 1.2.0 | 3 / 1 | |
| 1.1.0 | 3 / 1 | |
| 1.0.0 | 3 / 1 |
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
3 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.