← Home

path-extra

path-extra contains methods that aren't included in the vanilla Node.js path package.

19
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

jprichardsonryanzim

Keywords

fsfilefile systempath

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition from jprichardson to ryanzim in 2017; ryanzim is a well-established publisher with strong track record. ai
maintainer-change maintainer-added AI (maintainer-change): ryanzim added as maintainer in 2017; long-standing trusted publisher with 155 approved packages. ai

Versions (showing 19 of 19)

Version Deps Published
4.3.0 2 / 2
4.2.1 2 / 2
4.2.0 2 / 2
4.1.0 2 / 2
4.0.0 2 / 2
3.0.0 0 / 2
2.0.0 0 / 2
1.0.3 0 / 2
1.0.2 0 / 2
1.0.1 0 / 2
1.0.0 0 / 2
0.3.0 0 / 1
0.2.1 0 / 1
0.2.0 0 / 1
0.1.1 0 / 1
0.1.0 0 / 1
0.0.3 0 / 1
0.0.2 0 / 3
0.0.1 2 / 0

v4.3.0

1 finding
LOW No provenance attestation provenance

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

v4.2.1

1 finding
LOW No provenance attestation provenance

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

v4.2.0

2 findings
HIGH Publisher changed: jprichardson → ryanzim (on 2017-06-24) provenance

This version was published by a different npm account than previous versions on 2017-06-24. 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.

v4.1.0

2 findings
HIGH Publisher changed: jprichardson → ryanzim (on 2017-03-07) provenance

This version was published by a different npm account than previous versions on 2017-03-07. 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.

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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