parse-domain 2.2.0

Splits an url into sub-domain, domain and effective top-level-domain

parse-domain@2.2.0 was published on 2019-05-27. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: 2.2.0 is broken, see https://github.com/peerigon/parse-domain/issues/72

All parse-domain versions · Permanent reference to 2.2.0 · Latest release

Package specifications

Version2.2.0
License declarationUnlicense
Published2019-05-27T22:22:23.975Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size606.00 KiB
Published file count33
Package typeNot declared
ES module entryNot declared
Default entry./lib/parseDomain.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies229
Repository stars517
Repository forks70

Install parse-domain 2.2.0

npm install parse-domain@2.2.0
pnpm add parse-domain@2.2.0
yarn add parse-domain@2.2.0

Runtime dependencies

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.

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.

Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Pinned-Dependencies10/10 — all dependencies are pinned
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness