JavaScript API to work against complex domain names, subdomains and URIs.
65%
Total Score
50
100
90
70
50
No build attestation or trusted-publisher identity is present, reducing publication transparency. This is a provenance gap rather than evidence that the release is unsafe.
Install-time scripts include postinstall, prepack, and prepublish. These add build and installation complexity, though the package documentation describes an update-rules installation flow that makes lifecycle use plausible.
Only one registry account has publish access. That is a limited publishing base, although the linked repository and release history show an established project.
The repository is owned by an individual user rather than an organization, so there is no organizational backing to offset the single-publisher and contributor-base concerns.
The package has 35 releases over more than 14 years, but no releases in the last 12 months; this indicates a mature project with currently slow release activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
punycode Version ^2.0.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.