@blocklet/pages-kit-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 — 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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in UMD component loader to execute bundled component code; stable pattern for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Blob URL dynamic import in component loader; not arbitrary module loading from user input. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Listed as both dependency and peerDependency; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Listed as both dependency and peerDependency; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Declared dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Used as build tool dependency; phantom-dep heuristic false positive. | ai |
Versions (showing 51 of 196)
| Version | Deps | Published |
|---|---|---|
| 0.7.39 | 5 / 19 | |
| 0.7.38 | 5 / 19 | |
| 0.7.37 | 5 / 19 | |
| 0.7.36 | 5 / 19 | |
| 0.7.35 | 5 / 19 | |
| 0.7.34 | 5 / 19 | |
| 0.7.33 | 5 / 19 | |
| 0.7.32 | 5 / 19 | |
| 0.7.31 | 5 / 19 | |
| 0.7.30 | 5 / 19 | |
| 0.7.29 | 5 / 19 | |
| 0.7.28 | 5 / 19 | |
| 0.7.27 | 5 / 19 | |
| 0.7.26 | 5 / 19 | |
| 0.7.25 | 5 / 19 | |
| 0.7.24 | 5 / 19 | |
| 0.7.23 | 5 / 19 | |
| 0.7.22 | 5 / 19 | |
| 0.7.21 | 5 / 19 | |
| 0.7.20 | 5 / 19 | |
| 0.7.19 | 5 / 19 | |
| 0.7.18 | 5 / 19 | |
| 0.7.17 | 5 / 19 | |
| 0.7.16 | 5 / 19 | |
| 0.7.15 | 5 / 19 | |
| 0.7.14 | 5 / 19 | |
| 0.7.13 | 5 / 19 | |
| 0.7.12 | 5 / 19 | |
| 0.7.11 | 5 / 19 | |
| 0.7.10 | 5 / 19 | |
| 0.7.9 | 5 / 19 | |
| 0.7.8 | 5 / 19 | |
| 0.7.7 | 5 / 19 | |
| 0.7.6 | 5 / 19 | |
| 0.7.5 | 5 / 19 | |
| 0.7.4 | 5 / 19 | |
| 0.7.3 | 5 / 19 | |
| 0.7.2 | 5 / 19 | |
| 0.7.1 | 5 / 19 | |
| 0.7.0 | 5 / 19 | |
| 0.6.107 | 5 / 19 | |
| 0.6.106 | 5 / 19 | |
| 0.6.105 | 5 / 19 | |
| 0.6.104 | 5 / 19 | |
| 0.6.103 | 5 / 19 | |
| 0.6.102 | 5 / 19 | |
| 0.6.101 | 5 / 19 | |
| 0.6.100 | 5 / 19 | |
| 0.6.99 | 5 / 19 | |
| 0.6.98 | 5 / 19 | |
| 0.6.97 | 5 / 19 |
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. 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
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. Consider requesting the maintainer enable provenance via CI/CD.
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.