@blocklet/pages-kit-inner-components
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/cjs/chunks/home-FbBl1G79.js | AI (source-diff): Standard Vite/Rollup minified bundle output for a React UI library; not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/chunks/publish-button-JUoM34Aa.js | AI (source-diff): Standard Vite/Rollup minified bundle output for a React UI library; not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/es/chunks/index-BZ1MijZ6.js | AI (source-diff): Standard Vite/Rollup minified bundle output for a React UI library; not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/chunks/index-B-TdKJtn.js | AI (source-diff): Standard Vite/Rollup minified bundle output for a React UI library; not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/chunks/state-BBnuCgyl.js | AI (source-diff): Standard Vite minified bundle output; readable React/MUI code in samples, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/chunks/home-BQZXyZ-m.js | AI (source-diff): Standard Vite minified bundle output; readable React/MUI code in samples, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/chunks/index-ByDnzW6o.js | AI (source-diff): Standard Vite minified bundle output; readable React/MUI code in samples, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/es/chunks/index-EWs_19jE.js | AI (source-diff): Standard Vite minified bundle output; readable React/MUI code in samples, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/chunks/publish-button-Dv9qNYUI.js | AI (source-diff): Standard Vite minified bundle output; readable React/MUI code in samples, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/cjs/chunks/site-state-oC_X_C59.js | AI (source-diff): Standard Vite minified bundle output; readable React/MUI code in samples, not obfuscation. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): Large monorepo component; phantom deps reflect bundled/transitive usage, not missing imports. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer dep; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Same pattern — bundled component library with transitive deps. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Same pattern — bundled component library with transitive deps. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Same pattern — bundled component library with transitive deps. | ai | |
| phantom-deps | phantom-dep:jss | AI (phantom-deps): Same pattern — bundled component library with transitive deps. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.7.38 | 134 / 39 | |
| 0.7.37 | 134 / 39 | |
| 0.7.36 | 134 / 39 | |
| 0.7.35 | 134 / 39 | |
| 0.7.30 | 134 / 39 | |
| 0.7.29 | 134 / 39 | |
| 0.7.28 | 134 / 39 | |
| 0.7.27 | 134 / 39 | |
| 0.7.26 | 134 / 39 | |
| 0.7.25 | 134 / 39 | |
| 0.7.24 | 134 / 39 | |
| 0.7.23 | 134 / 39 | |
| 0.7.22 | 134 / 39 | |
| 0.7.21 | 134 / 39 | |
| 0.7.20 | 134 / 39 | |
| 0.7.19 | 134 / 39 | |
| 0.7.18 | 134 / 39 | |
| 0.7.17 | 134 / 39 | |
| 0.7.16 | 134 / 39 | |
| 0.5.9 | 138 / 40 | |
| 0.5.7 | 138 / 40 |
v0.7.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.35
7 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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
7 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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
7 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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
7 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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
7 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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.