@stdlib/fs-resolve-parent-path
Resolve a path by walking parent directories.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:tape | AI (npm-metadata): Dev-only test dep pinned to a fork branch; not shipped, stable across stdlib releases. | ai | |
| phantom-deps | phantom-dep:@stdlib/cli | AI (phantom-deps): Same-org stdlib dep, false positive pattern for this monorepo. | ai | |
| phantom-deps | phantom-dep:@stdlib/fs-read-file | AI (phantom-deps): Same-org stdlib dep, false positive pattern for this monorepo. | ai | |
| dependencies | unvetted-dep:@stdlib/assert-is-string | AI (dependencies): Sibling stdlib package; modular monorepo pattern, not a threat. | ai | |
| dependencies | unvetted-dep:@stdlib/assert-is-function | AI (dependencies): Sibling stdlib package; modular monorepo pattern, not a threat. | ai | |
| dependencies | unvetted-dep:@stdlib/fs-exists | AI (dependencies): Sibling stdlib package; modular monorepo pattern, not a threat. | ai | |
| dependencies | unvetted-dep:@stdlib/utils-define-nonenumerable-read-only-property | AI (dependencies): Sibling stdlib package; modular monorepo pattern, not a threat. | ai | |
| dependencies | unvetted-dep:@stdlib/assert-is-plain-object | AI (dependencies): Sibling stdlib package; modular monorepo pattern, not a threat. | ai | |
| dependencies | unvetted-dep:@stdlib/process-cwd | AI (dependencies): Sibling stdlib package; modular monorepo pattern, not a threat. | ai | |
| dependencies | unvetted-dep:@stdlib/string-format | AI (dependencies): Sibling stdlib package; modular monorepo pattern, not a threat. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 9 / 0 | |
| 0.2.2 | 9 / 0 | |
| 0.2.1 | 8 / 0 | |
| 0.2.0 | 8 / 4 | |
| 0.1.1 | 8 / 4 | |
| 0.1.0 | 8 / 4 | |
| 0.0.8 | 9 / 11 | |
| 0.0.7 | 9 / 11 | |
| 0.0.6 | 9 / 11 | |
| 0.0.5 | 9 / 11 | |
| 0.0.4 | 9 / 11 | |
| 0.0.3 | 9 / 11 | |
| 0.0.2 | 9 / 10 | |
| 0.0.1 | 9 / 10 |
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.