← Home

lodash.findkey

npm Repository Homepage

The lodash method `_.findKey` exported as a module.

21
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jdaltonmathiasphated

Keywords

lodash-modularizedfindkey

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): jdalton is the canonical lodash author; removal of kitcambridge and d10 reflects the lodash v4 team restructuring, not a takeover. ai
publish-pattern new-deps-added AI (publish-pattern): New deps are all legitimate lodash sub-packages added as part of the v3→v4 architectural refactor of the lodash modularized ecosystem. ai
source-diff source-size-tripled AI (source-diff): Size increase is consistent with lodash v4 modularization changes; no obfuscation or encoding signals present. ai

Versions (showing 21 of 21)

Version Deps Published
4.6.0 0 / 0
4.5.1 0 / 0
4.5.0 0 / 0
4.4.0 4 / 0
4.3.0 4 / 0
4.2.1 4 / 0
4.2.0 4 / 0
4.1.1 9 / 0
4.1.0 9 / 0
4.0.2 8 / 0
4.0.1 8 / 0
4.0.0 8 / 0
3.0.1 4 / 0
3.0.0 4 / 0
2.4.1 2 / 0
2.4.0 2 / 0
2.3.0 2 / 0
2.2.1 2 / 0
2.2.0 2 / 0
2.1.0 2 / 0
2.0.0 2 / 0

v4.6.0

1 finding
LOW No provenance attestation provenance

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

v4.5.1

1 finding
LOW No provenance attestation provenance

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

v4.5.0

1 finding
LOW No provenance attestation provenance

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

v4.4.0

1 finding
LOW No provenance attestation provenance

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

v4.3.0

1 finding
LOW No provenance attestation provenance

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

v4.2.1

1 finding
LOW No provenance attestation provenance

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

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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