@letsscrapedata/controller
Unified browser / HTML controller interfaces that support patchright, camoufox, playwright, puppeteer and cheerio
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): tsup bundler output, matches build script; not true obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Established browser-automation libs matching package's stated purpose. | ai | |
| dependencies | unvetted-dep:patchright | AI (dependencies): patchright is a known anti-detection Playwright fork; its use is consistent with this scraping controller package's purpose. | ai | |
| dependencies | unvetted-dep:camoufox-js-lsd | AI (dependencies): camoufox-js-lsd is the JS binding for Camoufox anti-detection browser; expected dependency for this scraping controller. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 82 versions; publisher hasn't adopted Sigstore attestation but no other risk signals present. | ai |
Versions (showing 51 of 79)
| Version | Deps | Published |
|---|---|---|
| 0.9.1 | 6 / 3 | |
| 0.9.0 | 6 / 3 | |
| 0.8.1 | 6 / 3 | |
| 0.8.0 | 6 / 3 | |
| 0.7.0 | 6 / 3 | |
| 0.6.5 | 6 / 3 | |
| 0.6.3 | 6 / 3 | |
| 0.6.2 | 6 / 3 | |
| 0.6.0 | 6 / 3 | |
| 0.5.0 | 6 / 3 | |
| 0.2.0 | 6 / 3 | |
| 0.1.0 | 6 / 3 | |
| 0.0.71 | 6 / 3 | |
| 0.0.67 | 9 / 3 | |
| 0.0.66 | 9 / 3 | |
| 0.0.65 | 9 / 3 | |
| 0.0.64 | 9 / 3 | |
| 0.0.63 | 9 / 3 | |
| 0.0.61 | 9 / 3 | |
| 0.0.60 | 9 / 3 | |
| 0.0.59 | 9 / 3 | |
| 0.0.58 | 9 / 3 | |
| 0.0.57 | 9 / 3 | |
| 0.0.56 | 8 / 3 | |
| 0.0.55 | 8 / 3 | |
| 0.0.54 | 8 / 3 | |
| 0.0.53 | 8 / 3 | |
| 0.0.52 | 7 / 3 | |
| 0.0.51 | 7 / 3 | |
| 0.0.50 | 7 / 3 | |
| 0.0.49 | 7 / 3 | |
| 0.0.48 | 7 / 3 | |
| 0.0.47 | 7 / 3 | |
| 0.0.46 | 7 / 3 | |
| 0.0.45 | 7 / 3 | |
| 0.0.44 | 7 / 3 | |
| 0.0.43 | 7 / 3 | |
| 0.0.42 | 7 / 3 | |
| 0.0.41 | 7 / 3 | |
| 0.0.40 | 7 / 3 | |
| 0.0.39 | 7 / 3 | |
| 0.0.38 | 7 / 3 | |
| 0.0.37 | 6 / 1 | |
| 0.0.36 | 6 / 1 | |
| 0.0.35 | 6 / 1 | |
| 0.0.34 | 6 / 1 | |
| 0.0.33 | 6 / 1 | |
| 0.0.32 | 6 / 1 | |
| 0.0.31 | 6 / 1 | |
| 0.0.30 | 6 / 1 | |
| 0.0.29 | 6 / 1 |
v0.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.