← Home

lodash.capitalize

npm Repository Homepage

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

12
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-modularizedcapitalize

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): mathias (Mathias Bynens) and phated (Blaine Bublitz) are well-known, legitimate lodash team contributors listed in package.json contributors. Not a takeover concern. ai
publish-pattern new-deps-added AI (publish-pattern): lodash.upperfirst is a legitimate lodash modular package replacing an internal helper; consistent with lodash v4 refactoring. ai
source-diff source-size-tripled AI (source-diff): Size increase from 898B to 3KB is explained by v4 refactoring inlining more logic. Total size is still tiny with no injected payload indicators. ai

Versions (showing 12 of 12)

Version Deps Published
4.2.1 0 / 0
4.2.0 0 / 0
4.1.1 2 / 0
4.1.0 2 / 0
4.0.3 1 / 0
4.0.2 1 / 0
4.0.1 1 / 0
4.0.0 1 / 0
3.1.2 1 / 0
3.1.1 1 / 0
3.1.0 1 / 0
3.0.0 1 / 0

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.3

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.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

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