@blocklet/pages-kit-runtime
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:glob | AI (phantom-deps): Build-tool utility; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Declared runtime dep used via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): CLI utility dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Utility dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): Known implicit binary dep; expected for build tooling. | ai | |
| phantom-deps | phantom-dep:gogocode | AI (phantom-deps): Code-transform dep used via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer/runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build toolchain dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@mdx-js/react | AI (phantom-deps): Runtime dep used via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-router-dom | AI (phantom-deps): Runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@mui/icons-material | AI (phantom-deps): UI dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:vite-plugin-react-pages | AI (phantom-deps): Build plugin dep; phantom-dep heuristic false positive. | ai |
Versions (showing 100 of 196)
| Version | Deps | Published |
|---|---|---|
| 0.7.39 | 20 / 10 | |
| 0.7.38 | 20 / 10 | |
| 0.7.37 | 20 / 10 | |
| 0.7.36 | 20 / 10 | |
| 0.7.35 | 20 / 10 | |
| 0.7.34 | 20 / 10 | |
| 0.7.33 | 20 / 10 | |
| 0.7.32 | 20 / 10 | |
| 0.7.31 | 20 / 10 | |
| 0.7.30 | 20 / 10 | |
| 0.7.29 | 20 / 10 | |
| 0.7.28 | 20 / 10 | |
| 0.7.27 | 20 / 10 | |
| 0.7.26 | 20 / 10 | |
| 0.7.25 | 20 / 10 | |
| 0.7.24 | 20 / 10 | |
| 0.7.23 | 20 / 10 | |
| 0.7.22 | 20 / 10 | |
| 0.7.21 | 20 / 10 | |
| 0.7.20 | 20 / 10 | |
| 0.7.19 | 20 / 10 | |
| 0.7.18 | 20 / 10 | |
| 0.7.17 | 20 / 10 | |
| 0.7.16 | 20 / 10 | |
| 0.7.15 | 20 / 10 | |
| 0.7.14 | 20 / 10 | |
| 0.7.13 | 20 / 10 | |
| 0.7.12 | 20 / 10 | |
| 0.7.11 | 20 / 10 | |
| 0.7.10 | 20 / 10 | |
| 0.7.9 | 20 / 10 | |
| 0.7.8 | 20 / 10 | |
| 0.7.7 | 20 / 10 | |
| 0.7.6 | 20 / 10 | |
| 0.7.5 | 20 / 10 | |
| 0.7.4 | 20 / 10 | |
| 0.7.3 | 20 / 10 | |
| 0.7.2 | 20 / 10 | |
| 0.7.1 | 20 / 10 | |
| 0.7.0 | 20 / 10 | |
| 0.6.107 | 20 / 10 | |
| 0.6.106 | 20 / 10 | |
| 0.6.105 | 20 / 10 | |
| 0.6.104 | 20 / 10 | |
| 0.6.103 | 20 / 10 | |
| 0.6.102 | 20 / 10 | |
| 0.6.101 | 20 / 10 | |
| 0.6.100 | 20 / 10 | |
| 0.6.99 | 20 / 10 | |
| 0.6.98 | 20 / 10 | |
| 0.6.97 | 20 / 10 | |
| 0.6.96 | 20 / 10 | |
| 0.6.95 | 20 / 10 | |
| 0.6.94 | 20 / 10 | |
| 0.6.93 | 20 / 10 | |
| 0.6.92 | 20 / 10 | |
| 0.6.91 | 20 / 10 | |
| 0.6.90 | 20 / 10 | |
| 0.6.89 | 20 / 10 | |
| 0.6.88 | 20 / 10 | |
| 0.6.87 | 20 / 10 | |
| 0.6.86 | 20 / 10 | |
| 0.6.85 | 20 / 10 | |
| 0.6.84 | 20 / 10 | |
| 0.6.83 | 20 / 10 | |
| 0.6.82 | 20 / 10 | |
| 0.6.81 | 20 / 10 | |
| 0.6.80 | 20 / 10 | |
| 0.6.79 | 20 / 10 | |
| 0.6.78 | 20 / 10 | |
| 0.6.77 | 20 / 10 | |
| 0.6.76 | 20 / 10 | |
| 0.6.75 | 20 / 10 | |
| 0.6.74 | 20 / 10 | |
| 0.6.73 | 20 / 10 | |
| 0.6.72 | 20 / 10 | |
| 0.6.71 | 20 / 10 | |
| 0.6.70 | 20 / 10 | |
| 0.6.69 | 20 / 10 | |
| 0.6.68 | 20 / 10 | |
| 0.6.67 | 20 / 10 | |
| 0.6.66 | 20 / 10 | |
| 0.6.65 | 20 / 10 | |
| 0.6.64 | 20 / 10 | |
| 0.6.63 | 20 / 10 | |
| 0.6.62 | 20 / 10 | |
| 0.6.61 | 20 / 10 | |
| 0.6.60 | 20 / 10 | |
| 0.6.59 | 20 / 10 | |
| 0.6.58 | 20 / 10 | |
| 0.6.57 | 20 / 10 | |
| 0.6.56 | 20 / 10 | |
| 0.6.55 | 20 / 10 | |
| 0.6.53 | 20 / 10 | |
| 0.6.52 | 20 / 10 | |
| 0.6.51 | 20 / 10 | |
| 0.6.50 | 20 / 10 | |
| 0.6.49 | 20 / 10 | |
| 0.6.48 | 20 / 10 | |
| 0.6.47 | 20 / 10 |
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
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
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v0.6.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.