An implementation of the WHATWG URL Standard's URL API and parsing machinery
86%
Total Score
healthy
Healthy: long-running, actively maintained releases and a current, non-archived source project.
A prepare script runs during installation, adding install-time behavior that consumers should account for. The signal provides no evidence that the script is unsafe, so this is only a modest hygiene concern.
The project uses npm scripts and esbuild, but no security-scanning tools were detected. The missing scanning is a hygiene gap, while the build tooling itself is established and explicit.
No type declarations are published, which is a minor integration gap for consumers using TypeScript. It does not indicate abandonment or a supply-chain weakness.
All three workflows were analyzed, with no untrusted checkout or script-injection findings. However, all 9 action references are unpinned and two workflows grant top-level write permissions; the sole cache-poisoning finding is low confidence, so it is hygiene rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tr46 Version ^7.0.0 | — | — |
@exodus/bytes Version ^1.16.0 | — | — |
webidl-conversions Version ^8.0.1 | — | — |
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.