@blocklet/pages-kit
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@blocklet/ai-kit | AI (dependencies): Same-org Arcblock/Blocklet package; consistent with the rest of the dependency tree. | ai | |
| dependencies | unvetted-dep:@arcblock/did-connect | AI (dependencies): Same-org Arcblock package; part of the established Blocklet ecosystem. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Declared in package.json for config/peer use; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lottiefiles/lottie-player | AI (phantom-deps): Declared for config/peer use; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:material-ui-popup-state | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@iconify-icons/tabler | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-frame-component | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-promise-suspense | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-transition-group | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:jsonata | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:file-saver | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:html2pdf.js | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-share | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@faker-js/faker | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:es-module-shims | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@blocklet/js-sdk | AI (phantom-deps): Same-org scoped dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/file-saver | AI (phantom-deps): Framework-scoped type package; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:json-schema-faker | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/d3-dispatch | AI (phantom-deps): Framework-scoped type package; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@blocklet/aigne-sdk | AI (phantom-deps): Same-org scoped dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:isomorphic-dompurify | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Config-referenced validation library; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:joi | AI (phantom-deps): Config-referenced validation library; stable pattern for this package. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Fetch is guarded by multiple runtime conditions (cookie, feature flags, config values); not unconditional telemetry. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): React.lazy URL-based component loader pattern; expected for blocklet plugin renderer architecture. | ai |
Versions (showing 57 of 157)
| Version | Deps | Published |
|---|---|---|
| 0.6.46 | 53 / 24 | |
| 0.6.45 | 53 / 25 | |
| 0.6.44 | 53 / 25 | |
| 0.6.43 | 53 / 25 | |
| 0.6.42 | 53 / 25 | |
| 0.6.41 | 53 / 25 | |
| 0.6.40 | 53 / 25 | |
| 0.6.39 | 53 / 25 | |
| 0.6.38 | 53 / 25 | |
| 0.6.37 | 53 / 25 | |
| 0.6.36 | 53 / 25 | |
| 0.6.35 | 53 / 25 | |
| 0.6.34 | 53 / 25 | |
| 0.6.33 | 53 / 25 | |
| 0.6.32 | 53 / 25 | |
| 0.6.31 | 53 / 25 | |
| 0.6.30 | 53 / 25 | |
| 0.6.29 | 53 / 25 | |
| 0.6.28 | 53 / 25 | |
| 0.6.27 | 53 / 25 | |
| 0.6.26 | 53 / 25 | |
| 0.6.25 | 53 / 25 | |
| 0.6.24 | 53 / 25 | |
| 0.6.23 | 53 / 25 | |
| 0.6.22 | 53 / 25 | |
| 0.6.21 | 53 / 25 | |
| 0.6.20 | 53 / 25 | |
| 0.6.19 | 53 / 25 | |
| 0.6.18 | 52 / 25 | |
| 0.6.17 | 52 / 25 | |
| 0.6.16 | 52 / 25 | |
| 0.6.15 | 52 / 25 | |
| 0.6.14 | 52 / 25 | |
| 0.6.13 | 52 / 25 | |
| 0.6.12 | 52 / 25 | |
| 0.6.11 | 52 / 25 | |
| 0.6.10 | 52 / 25 | |
| 0.6.9 | 52 / 25 | |
| 0.6.8 | 52 / 25 | |
| 0.6.7 | 52 / 25 | |
| 0.6.6 | 52 / 25 | |
| 0.6.5 | 52 / 25 | |
| 0.6.4 | 52 / 25 | |
| 0.6.3 | 52 / 25 | |
| 0.6.2 | 52 / 25 | |
| 0.6.1 | 52 / 25 | |
| 0.6.0 | 52 / 25 | |
| 0.5.56 | 52 / 25 | |
| 0.5.55 | 52 / 25 | |
| 0.5.54 | 52 / 25 | |
| 0.5.53 | 52 / 25 | |
| 0.5.52 | 52 / 25 | |
| 0.5.19 | 51 / 25 | |
| 0.5.10 | 49 / 25 | |
| 0.5.9 | 49 / 25 | |
| 0.5.8 | 49 / 25 | |
| 0.5.7 | 49 / 25 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
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.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.