upath
A drop-in replacement / proxy to Node.js path, replacing \\ with / for all results & adding file extension functions.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from manual (anodynos) to GitHub Actions CI/CD with SLSA provenance — this is a security improvement, not a risk. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 3.0.7 | 0 / 15 | |
| 3.0.6 | 0 / 10 | |
| 3.0.5 | 0 / 10 | |
| 3.0.0 | 0 / 10 | |
| 2.0.1 | 0 / 12 | |
| 2.0.0 | 0 / 12 | |
| 1.2.0 | 0 / 12 | |
| 1.1.2 | 0 / 12 | |
| 1.1.1 | 0 / 12 | |
| 1.1.0 | 0 / 12 | |
| 1.0.5 | 0 / 12 | |
| 1.0.4 | 0 / 12 | |
| 1.0.3 | 4 / 12 | |
| 1.0.2 | 4 / 11 | |
| 1.0.0 | 2 / 9 | |
| 0.2.0 | 2 / 9 | |
| 0.1.7 | 2 / 9 | |
| 0.1.6 | 2 / 9 | |
| 0.1.5 | 2 / 9 | |
| 0.1.4 | 2 / 9 | |
| 0.1.3 | 2 / 9 | |
| 0.1.2 | 2 / 9 | |
| 0.1.1 | 2 / 9 | |
| 0.1.0 | 2 / 9 |
v3.0.6
2 findingsThis version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.