universal-url
WHATWG URL for Node & Browser.
universal-url@2.0.0 was published on 2018-11-28. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 6.
All universal-url versions · Permanent reference to 2.0.0
Package specifications
| Version | 2.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2018-11-28T16:32:39.696Z |
| Node.js requirement | >= 6 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 4.81 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 23 |
| Repository forks | 4 |
Install universal-url 2.0.0
npm install universal-url@2.0.0 pnpm add universal-url@2.0.0 yarn add universal-url@2.0.0
Runtime dependencies
- hasurl ^1.0.0
- whatwg-url ^7.0.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- hasurl@1.0.0 — direct
- lodash.sortby@4.7.0 — indirect
- punycode@2.3.1 — indirect
- tr46@1.0.1 — indirect
- webidl-conversions@4.0.2 — indirect
- whatwg-url@7.1.0 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| SAST | 0/10 — no SAST tool detected |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — project is archived |
| Code-Review | 0/10 — Found 0/6 approved changesets -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/universal-url/2.0.0 — retrieved 2026-10-29T12:44:20.921Z
- https://api.deps.dev/v3/systems/npm/packages/universal-url/versions/2.0.0:dependencies — retrieved 2026-10-29T12:44:21.461Z
- https://api.deps.dev/v3/systems/npm/packages/universal-url/versions/2.0.0 — retrieved 2026-10-29T12:44:21.433Z
- https://api.deps.dev/v3/projects/github.com%2Fstevenvachon%2Funiversal-url — retrieved 2026-10-29T12:44:21.597Z