@tangle-network/browser-agent-driver
LLM-driven browser agent for UI automation, testing, and evaluation
Supply chain provenance
Status for the latest visible version.
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/drivers/cursor-overlay.d.ts | AI (source-diff): Long line is a legitimate inline DOM/CSS script string in a .d.ts declaration file, not obfuscated malware. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate automation pattern for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Runs a local bundled .mjs script for provider patching; no remote code fetch; SLSA provenance attested. | ai | |
| phantom-deps | phantom-dep:openai | AI (phantom-deps): openai is a declared runtime dep; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:axe-core | AI (phantom-deps): axe-core is a declared runtime dep used via config injection; false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.32.0 | 9 / 13 | |
| 0.30.0 | 9 / 12 | |
| 0.21.0 | 8 / 12 | |
| 0.18.0 | 8 / 12 | |
| 0.16.0 | 8 / 12 | |
| 0.14.1 | 8 / 12 | |
| 0.12.1 | 7 / 10 | |
| 0.12.0 | 7 / 10 |
v0.32.0
2 findingsScript: node ./scripts/postinstall-provider-patches.mjs
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
3 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
3 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
3 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.