@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 51 of 157)
| Version | Deps | Published |
|---|---|---|
| 0.7.39 | 56 / 24 | |
| 0.7.38 | 56 / 24 | |
| 0.7.37 | 56 / 24 | |
| 0.7.36 | 56 / 24 | |
| 0.7.35 | 56 / 24 | |
| 0.7.34 | 56 / 24 | |
| 0.7.33 | 56 / 24 | |
| 0.7.32 | 56 / 24 | |
| 0.7.31 | 56 / 24 | |
| 0.7.30 | 56 / 24 | |
| 0.7.29 | 56 / 24 | |
| 0.7.28 | 56 / 24 | |
| 0.7.27 | 56 / 24 | |
| 0.7.26 | 56 / 24 | |
| 0.7.25 | 56 / 24 | |
| 0.7.24 | 56 / 24 | |
| 0.7.23 | 56 / 24 | |
| 0.7.22 | 56 / 24 | |
| 0.7.21 | 56 / 24 | |
| 0.7.20 | 56 / 24 | |
| 0.7.19 | 56 / 24 | |
| 0.7.18 | 56 / 24 | |
| 0.7.17 | 56 / 24 | |
| 0.7.16 | 56 / 24 | |
| 0.7.15 | 56 / 24 | |
| 0.7.14 | 56 / 24 | |
| 0.7.13 | 56 / 24 | |
| 0.7.12 | 56 / 24 | |
| 0.7.11 | 56 / 24 | |
| 0.7.10 | 56 / 24 | |
| 0.7.9 | 56 / 24 | |
| 0.7.8 | 56 / 24 | |
| 0.7.7 | 56 / 24 | |
| 0.7.6 | 56 / 24 | |
| 0.7.5 | 56 / 24 | |
| 0.7.4 | 56 / 24 | |
| 0.7.3 | 56 / 24 | |
| 0.7.2 | 56 / 24 | |
| 0.7.1 | 56 / 24 | |
| 0.7.0 | 56 / 24 | |
| 0.6.107 | 56 / 24 | |
| 0.6.106 | 56 / 24 | |
| 0.6.105 | 56 / 24 | |
| 0.6.104 | 55 / 24 | |
| 0.6.103 | 55 / 24 | |
| 0.6.102 | 55 / 24 | |
| 0.6.101 | 55 / 24 | |
| 0.6.100 | 55 / 24 | |
| 0.6.99 | 55 / 24 | |
| 0.6.98 | 55 / 24 | |
| 0.6.97 | 55 / 24 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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.