@blocklet/crawler
blocklet crawler lib
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Crawler utility legitimately uses child_process; consistent with puppeteer/headless browser orchestration in this package. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): prettier is a declared dep used in build/config tooling, not a runtime import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:url-join | AI (phantom-deps): Declared dep likely used in compiled output or config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lru-cache | AI (phantom-deps): Declared dep likely used in compiled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:p-wait-for | AI (phantom-deps): Declared dep likely used in compiled output; stable false positive for this package. | ai |
Versions (showing 8 of 208)
| Version | Deps | Published |
|---|---|---|
| 2.4.44 | 16 / 15 | |
| 2.3.67 | 16 / 15 | |
| 2.3.39 | 16 / 15 | |
| 2.3.17 | 16 / 15 | |
| 2.3.15 | 16 / 15 | |
| 2.3.9 | 16 / 15 | |
| 2.3.7 | 16 / 15 | |
| 2.3.6 | 16 / 15 |
v2.4.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.