resolve-file
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:npmrc-access | AI (semgrep): Fires on a JSDoc comment example path, not actual .npmrc access code; stable false positive for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 7 / 9 |
v0.3.0
3 findingsAccessing .npmrc can expose npm auth tokens Source: https://github.com/doowb/resolve-file/blob/0c041012ad034812194e01929c3c93c3e2f822dc/index.js#L20 18 | * - node module "main" file (`'cwd'`) 19 | * - specific file inside a node module (`'cwd/LICENSE'`) > 20 | * - file located in user's home directory (`'~/.npmrc'`) 21 | * 22 | * ```js
Accessing .npmrc can expose npm auth tokens Source: https://github.com/doowb/resolve-file/blob/0c041012ad034812194e01929c3c93c3e2f822dc/index.js#L45 43 | * - node module "main" file (`'cwd'`) 44 | * - specific file inside a node module (`'cwd/LICENSE'`) > 45 | * - file located in user's home directory (`'~/.npmrc'`) 46 | * 47 | * ```js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.