lodash.trim
The Lodash method `_.trim` exported as a module.
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): d10 and kitcambridge are historical lodash contributors who stepped back; jdalton remains the canonical maintainer. Not a takeover signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; published by the authoritative lodash maintainer jdalton. No provenance is expected for this era of publishing. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.18.0 | 0 / 0 | |
| 3.1.1 | 6 / 0 | |
| 3.1.0 | 2 / 0 | |
| 3.0.1 | 6 / 0 | |
| 3.0.0 | 6 / 0 |
v4.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package 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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.