A PAC file proxy `http.Agent` implementation for HTTP
67%
Total Score
50
88
75
100
The repository recorded zero commits and zero active maintainers in the last 3 months, a meaningful sign that maintenance activity has recently stalled despite the recent release history.
The repository name does not match the package and its README does not mention it, creating some uncertainty about package-to-repository alignment; the multi-package source tree partly explains the name mismatch but not the missing mention.
The project uses TypeScript, npm scripts, Vitest, and Turbo, showing structured build and test tooling, but no security-scanning tools were detected.
No repository security policy was found, reducing transparency for reporting and handling vulnerabilities.
All 13 analyzed action references are unpinned, and the release workflow installs a package outside a lockfile; the cache-poisoning findings are low-confidence hygiene observations rather than decisive evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
debug Version ^4.3.4 | — | — |
get-uri Version 8.0.1 | — | — |
agent-base Version 9.0.0 | — | — |
pac-resolver Version 9.0.1 | — | — |
quickjs-wasi Version ^2.2.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.