@blocklet/pages-kit-block-studio
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): Build tool; esbuild is a known implicit runtime/binary dependency for this package. | ai | |
| dependencies | unvetted-dep:ts-to-zod | AI (dependencies): ts-to-zod is a well-known TypeScript-to-Zod schema converter; use here is consistent with the package's schema generation utilities. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env into child_process spawn options is standard practice for inheriting env in build tools. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads a local package.json path in a Vite plugin — not arbitrary user-controlled input. | ai | |
| phantom-deps | phantom-dep:gogocode | AI (phantom-deps): Declared in package.json dependencies; used via config/scripts rather than direct import. | ai | |
| phantom-deps | phantom-dep:copyfiles | AI (phantom-deps): Used as a CLI tool in build scripts, not imported directly. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer/runtime dependency used by bundled React components, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@mdx-js/react | AI (phantom-deps): MDX peer dependency used at runtime by consumers, not directly imported in this package's source. | ai | |
| phantom-deps | phantom-dep:crypto-browserify | AI (phantom-deps): Polyfill declared for Vite bundling config, not directly imported in source. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Build-tool middleware spawning subprocesses is expected for this package's documented functionality. | ai |
Versions (showing 51 of 196)
| Version | Deps | Published |
|---|---|---|
| 0.7.39 | 35 / 12 | |
| 0.7.38 | 35 / 12 | |
| 0.7.37 | 35 / 12 | |
| 0.7.36 | 35 / 12 | |
| 0.7.35 | 35 / 12 | |
| 0.7.34 | 35 / 12 | |
| 0.7.33 | 35 / 12 | |
| 0.7.32 | 35 / 12 | |
| 0.7.31 | 35 / 12 | |
| 0.7.30 | 35 / 12 | |
| 0.7.29 | 35 / 12 | |
| 0.7.28 | 35 / 12 | |
| 0.7.27 | 35 / 12 | |
| 0.7.26 | 35 / 12 | |
| 0.7.25 | 35 / 12 | |
| 0.7.24 | 35 / 12 | |
| 0.7.23 | 35 / 12 | |
| 0.7.22 | 35 / 12 | |
| 0.7.21 | 35 / 12 | |
| 0.7.20 | 35 / 12 | |
| 0.7.19 | 35 / 12 | |
| 0.7.18 | 35 / 12 | |
| 0.7.17 | 35 / 12 | |
| 0.7.16 | 35 / 12 | |
| 0.7.15 | 35 / 12 | |
| 0.7.14 | 35 / 12 | |
| 0.7.13 | 35 / 12 | |
| 0.7.12 | 35 / 12 | |
| 0.7.11 | 35 / 12 | |
| 0.7.10 | 35 / 12 | |
| 0.7.9 | 35 / 12 | |
| 0.7.8 | 35 / 12 | |
| 0.7.7 | 35 / 12 | |
| 0.7.6 | 35 / 12 | |
| 0.7.5 | 35 / 12 | |
| 0.7.4 | 35 / 12 | |
| 0.7.3 | 35 / 12 | |
| 0.7.2 | 35 / 12 | |
| 0.7.1 | 35 / 12 | |
| 0.7.0 | 35 / 12 | |
| 0.6.107 | 35 / 12 | |
| 0.6.106 | 35 / 12 | |
| 0.6.105 | 35 / 12 | |
| 0.6.104 | 35 / 12 | |
| 0.6.103 | 35 / 12 | |
| 0.6.102 | 35 / 12 | |
| 0.6.101 | 35 / 12 | |
| 0.6.100 | 35 / 12 | |
| 0.6.99 | 35 / 12 | |
| 0.6.98 | 35 / 12 | |
| 0.6.97 | 35 / 12 |
v0.7.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.37
3 findingsSpreading entire process.env into an object — may capture all secrets 64 | stdio: 'inherit', 65 | shell: true, > 66 | env: { 67 | ...process.env, 68 | FORCE_COLOR: '1',
Spreading entire process.env into an object — may capture all secrets 61 | stdio: 'inherit', 62 | shell: true, > 63 | env: { 64 | ...process.env, 65 | FORCE_COLOR: '1',
Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.26
1 findingPackage 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.