← Home

parseurl

npm Repository Homepage

parse a url with memoization

11
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

dougwilson

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition from jongleberry to dougwilson within the Express.js project; both are well-known core maintainers. ai
maintainer-change maintainer-added AI (maintainer-change): Added maintainers are all known Express.js core team members (dougwilson, tjholowaychuk, etc.); legitimate team expansion. ai
bogus-package bogus-package AI (bogus-package): Tiny focused utility using only Node built-ins; no keywords/deps/large payload is expected for this package. ai

Versions (showing 11 of 11)

Version Deps Published
1.3.3 0 / 11
1.3.2 0 / 11
1.3.1 0 / 5
1.3.0 0 / 5
1.2.0 0 / 5
1.1.3 0 / 0
1.1.2 0 / 0
1.1.1 0 / 0
1.1.0 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0

v1.3.2

1 finding
LOW No provenance attestation provenance

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

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. 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.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

2 findings
HIGH Publisher changed: jongleberry → dougwilson (on 2014-07-09) provenance

This version was published by a different npm account than previous versions on 2014-07-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.1.1

2 findings
HIGH Publisher changed: jongleberry → dougwilson (on 2014-07-09) provenance

This version was published by a different npm account than previous versions on 2014-07-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.1.0

2 findings
HIGH Publisher changed: jongleberry → dougwilson (on 2014-07-09) provenance

This version was published by a different npm account than previous versions on 2014-07-09. This could indicate a legitimate maintainer transition or an account compromise.

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.