lodash.find
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): jdalton is the original lodash author; removal of kitcambridge and d10 reflects known lodash project consolidation around v4, not a takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are first-party lodash sub-packages consistent with the v4 major version refactor of lodash's modularized build. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from 3KB to 11KB is consistent with the lodash v3→v4 major rewrite; no obfuscation or injected payload indicators. | ai |
Versions (showing 23 of 23)
| 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.2.1 | 6 / 0 | |
| 3.2.0 | 6 / 0 | |
| 3.1.0 | 5 / 0 | |
| 3.0.0 | 5 / 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.