← Home

find-module-bin

npm Repository Homepage

scan known node_modules directories to find installation directory of a particular bin file

5
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

mateodelnorte

Keywords

scannode_modulesbinbinaryexecutablefile

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from mateodelnorte to patrickleet in 2018 appears to be a legitimate maintainer transition; patrickleet has 82 approved packages, no code changes were introduced, and no malicious signals are present. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Package is 9+ years old with a trusted publisher (107 approved packages). The 0.0.0 version is a historical artifact, not a malicious indicator. ai
bogus-package bogus-package AI (bogus-package): Small utility package with a clear, focused purpose. Tiny payload and no deps are expected for this type of helper. Legitimate use confirmed by age, downloads, and publisher history. ai

Versions (showing 5 of 5)

Version Deps Published
1.1.0 2 / 7
1.0.0 2 / 4
0.0.2 2 / 4
0.0.1 2 / 0
0.0.0 0 / 0

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

2 findings
HIGH Publisher changed: mateodelnorte → patrickleet (on 2018-12-23) provenance

This version was published by a different npm account than previous versions on 2018-12-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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.