← Home

@sailshq/lodash

npm Repository Homepage

A fork of Lodash 3.10.x with ongoing maintenance from the Sails core team.

6
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

mikermcneilrachaelshawirlsgress454eashawdominuskelvin

Keywords

lodash-3lodash3lodash-3.10.1lodash-3.10.x

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): eashaw is a long-standing, highly trusted npm account (851 approved packages) and a known Sails.js team member. Transition from mikermcneil is a legitimate internal handoff. ai
maintainer-change maintainer-added AI (maintainer-change): eashaw is a trusted Sails.js org member with strong track record; addition is consistent with legitimate team maintenance of this Sails.js fork. ai

Versions (showing 6 of 6)

Version Deps Published
3.10.7 0 / 0
3.10.6 0 / 0
3.10.5 0 / 0
3.10.4 0 / 0
3.10.3 0 / 0
3.10.2 0 / 0

v3.10.7

1 finding
LOW No provenance attestation provenance

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

v3.10.6

1 finding
LOW No provenance attestation provenance

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

v3.10.5

2 findings
HIGH Publisher changed: mikermcneil → eashaw (on 2024-04-01) provenance

This version was published by a different npm account than previous versions on 2024-04-01. 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.

v3.10.4

2 findings
HIGH Publisher changed: mikermcneil → rachaelshaw (on 2019-08-21) provenance

This version was published by a different npm account than previous versions on 2019-08-21. 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.

v3.10.3

1 finding
LOW No provenance attestation provenance

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

v3.10.2

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.