← Home

bidirectional-resolve

npm Repository Homepage

Resolve a package entry point to a file path (like require.resolve/import.meta.resolve) OR a file path to a package entry point

2
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

xunnamius

Keywords

inversereversebidirectionalenhancedadvancedresolverequireimportnodemodulepackagecjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:escape-string-regexp~4 AI (dependencies): escape-string-regexp v4 is a well-known sindresorhus utility; aliased name is a common npm pattern, not suspicious. ai

Versions (showing 2 of 2)

Version Deps Published
2.0.4 3 / 5
2.0.3 3 / 3

v2.0.4

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.

v2.0.3

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.