uri-js
An RFC 3986/3987 compliant, scheme extendable URI/IRI parsing/validating/resolving library for JavaScript.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.4.1 | 1 / 11 | |
| 4.4.0 | 1 / 11 | |
| 4.3.0 | 1 / 11 | |
| 4.2.2 | 1 / 11 | |
| 4.2.1 | 1 / 11 | |
| 4.2.0 | 1 / 11 | |
| 3.0.2 | 1 / 11 | |
| 3.0.1 | 1 / 11 | |
| 3.0.0 | 1 / 11 | |
| 2.1.1 | 0 / 8 | |
| 2.1.0 | 0 / 8 | |
| 2.0.0 | 0 / 7 | |
| 1.4.2 | 0 / 0 | |
| 1.4.0 | 0 / 0 |
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.