absolute-path
Node.js 0.11.x path.isAbsolute as a separate module
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
filearts
Keywords
pathabsoluteisabsolutewindows
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package has been at 0.0.0 for 12+ years with 2 approved dependents; this is a stable micro-utility, not a throwaway malicious package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tiny payload and minimal README are expected for a single-function path utility polyfill; 2 approved inbound edges confirm legitimate ecosystem use. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.0.0 | 0 / 0 |
v0.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.