@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 96 of 196)
| Version | Deps | Published |
|---|---|---|
| 0.6.46 | 5 / 19 | |
| 0.6.45 | 5 / 19 | |
| 0.6.44 | 5 / 19 | |
| 0.6.43 | 5 / 19 | |
| 0.6.42 | 5 / 19 | |
| 0.6.41 | 5 / 19 | |
| 0.6.40 | 5 / 19 | |
| 0.6.39 | 5 / 19 | |
| 0.6.38 | 5 / 19 | |
| 0.6.37 | 5 / 19 | |
| 0.6.36 | 5 / 19 | |
| 0.6.35 | 5 / 19 | |
| 0.6.34 | 5 / 19 | |
| 0.6.33 | 5 / 19 | |
| 0.6.32 | 5 / 19 | |
| 0.6.31 | 5 / 19 | |
| 0.6.30 | 5 / 19 | |
| 0.6.29 | 5 / 19 | |
| 0.6.28 | 5 / 19 | |
| 0.6.27 | 5 / 19 | |
| 0.6.26 | 5 / 19 | |
| 0.6.25 | 5 / 19 | |
| 0.6.24 | 5 / 19 | |
| 0.6.23 | 5 / 19 | |
| 0.6.22 | 5 / 19 | |
| 0.6.21 | 5 / 19 | |
| 0.6.20 | 5 / 19 | |
| 0.6.19 | 5 / 19 | |
| 0.6.18 | 5 / 19 | |
| 0.6.17 | 5 / 19 | |
| 0.6.16 | 5 / 19 | |
| 0.6.15 | 5 / 19 | |
| 0.6.14 | 5 / 19 | |
| 0.6.13 | 5 / 19 | |
| 0.6.12 | 5 / 19 | |
| 0.6.11 | 5 / 19 | |
| 0.6.10 | 5 / 19 | |
| 0.6.9 | 5 / 19 | |
| 0.6.8 | 5 / 19 | |
| 0.6.7 | 5 / 19 | |
| 0.6.6 | 5 / 19 | |
| 0.6.5 | 5 / 19 | |
| 0.6.4 | 5 / 19 | |
| 0.6.3 | 5 / 19 | |
| 0.6.2 | 5 / 19 | |
| 0.6.1 | 5 / 19 | |
| 0.6.0 | 5 / 19 | |
| 0.5.56 | 5 / 19 | |
| 0.5.55 | 5 / 19 | |
| 0.5.54 | 5 / 19 | |
| 0.5.53 | 5 / 19 | |
| 0.5.52 | 5 / 19 | |
| 0.5.51 | 5 / 19 | |
| 0.5.50 | 5 / 19 | |
| 0.5.49 | 5 / 19 | |
| 0.5.48 | 5 / 19 | |
| 0.5.47 | 5 / 19 | |
| 0.5.45 | 5 / 19 | |
| 0.5.44 | 5 / 19 | |
| 0.5.43 | 5 / 19 | |
| 0.5.42 | 5 / 19 | |
| 0.5.41 | 5 / 19 | |
| 0.5.40 | 5 / 19 | |
| 0.5.39 | 5 / 19 | |
| 0.5.38 | 5 / 19 | |
| 0.5.37 | 5 / 19 | |
| 0.5.36 | 5 / 19 | |
| 0.5.35 | 5 / 19 | |
| 0.5.34 | 5 / 19 | |
| 0.5.33 | 5 / 19 | |
| 0.5.32 | 5 / 19 | |
| 0.5.31 | 5 / 19 | |
| 0.5.30 | 4 / 11 | |
| 0.5.29 | 4 / 11 | |
| 0.5.28 | 4 / 11 | |
| 0.5.27 | 4 / 11 | |
| 0.5.26 | 4 / 11 | |
| 0.5.25 | 4 / 11 | |
| 0.5.24 | 4 / 11 | |
| 0.5.23 | 4 / 11 | |
| 0.5.22 | 4 / 11 | |
| 0.5.21 | 4 / 11 | |
| 0.5.20 | 4 / 11 | |
| 0.5.19 | 4 / 11 | |
| 0.5.18 | 4 / 11 | |
| 0.5.17 | 4 / 11 | |
| 0.5.16 | 4 / 11 | |
| 0.5.15 | 4 / 11 | |
| 0.5.14 | 4 / 11 | |
| 0.5.13 | 4 / 11 | |
| 0.5.12 | 4 / 11 | |
| 0.5.11 | 4 / 11 | |
| 0.5.10 | 4 / 11 | |
| 0.5.9 | 4 / 11 | |
| 0.5.8 | 4 / 11 | |
| 0.5.7 | 4 / 11 |
v0.6.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.8
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.