look-up — Greenflagged

Faster drop-in replacement for find-up and findup-sync.

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

jonschlinkertdoowb

Keywords

filefindfind-upfindupgloblookmatchpackagepackage.jsonpatternresolvesearchsyncup

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): doowb is a known collaborator in the jonschlinkert ecosystem; this is a routine legitimate maintainer addition, not a suspicious takeover.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package is 4199 days old and predates Sigstore provenance; absence of attestation is expected and not a risk signal for this established package.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require() is in benchmark/check.js only — a test/benchmark file iterating over code samples. Not reachable by consumers; stable false positive for this package.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): New dep is 'multimatch', a well-known legitimate utility by the same maintainer (jonschlinkert). Not a suspicious addition.	ai	2026/04/24

Versions (showing 20 of 20)

Version	Deps	Published
0.8.3	5 / 15	2016-02-04
0.8.2	5 / 15	2015-11-21
0.8.1	5 / 16	2015-10-04
0.8.0	5 / 16	2015-10-04
0.7.2	3 / 8	2015-09-12
0.7.1	3 / 8	2015-04-07
0.7.0	3 / 8	2015-03-10
0.6.0	3 / 8	2015-02-05
0.5.2	2 / 7	2015-02-01
0.5.0	2 / 7	2015-01-19
0.4.1	2 / 7	2014-12-18
0.4.0	3 / 6	2014-12-18
0.3.1	2 / 5	2014-12-13
0.3.0	2 / 5	2014-12-13
0.2.3	2 / 5	2014-12-10
0.2.2	2 / 5	2014-12-01
0.2.1	2 / 5	2014-12-01
0.2.0	2 / 5	2014-12-01
0.1.1	2 / 6	2014-10-24
0.1.0	1 / 7	2014-10-24

v0.8.3

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

INFO No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.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.