← Home

@hyperjump/uri

npm Repository Homepage

A small and fast library for validating parsing and resolving URIs and IRIs

10
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

jason.desrosiers

Keywords

URIIRIresolverelativeparseRFC3986RFC-3986RFC3987RFC-3987

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:uuid AI (typosquat): @hyperjump/uri is a legitimate URI/IRI library under the hyperjump org scope; Levenshtein match against 'uuid' is a false positive with no impersonation intent. ai
typosquat typosquat.levenshtein:joi AI (typosquat): @hyperjump/uri is a legitimate URI/IRI library under the hyperjump org scope; Levenshtein match against 'joi' is a false positive with no impersonation intent. ai

Versions (showing 10 of 10)

Version Deps Published
1.3.4 0 / 6
1.3.3 0 / 6
1.3.2 0 / 6
1.3.1 0 / 6
1.3.0 0 / 5
1.2.2 0 / 12
1.2.1 0 / 5
1.2.0 0 / 5
1.1.0 0 / 5
1.0.0 0 / 5

v1.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.