← Home

lodash.groupby

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

23
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-modularizedgroupby

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): jdalton (original lodash author) remains publisher; removal of kitcambridge and d10 reflects the lodash 4.x team reorganization, not a takeover. ai
publish-pattern new-deps-added AI (publish-pattern): All new deps are official lodash modularized sub-packages consistent with lodash 4.x decomposition strategy, published by the same trusted author. ai
source-diff source-size-tripled AI (source-diff): Size increase from 2KB to 12KB reflects lodash 4.x major version feature expansion; no obfuscation or encoding signals present. 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 2 / 0
4.3.0 2 / 0
4.2.1 2 / 0
4.2.0 2 / 0
4.1.1 7 / 0
4.1.0 7 / 0
4.0.3 6 / 0
4.0.2 6 / 0
4.0.1 6 / 0
4.0.0 6 / 0
3.1.1 2 / 0
3.1.0 2 / 0
3.0.0 1 / 0
2.4.1 1 / 0
2.4.0 1 / 0
2.3.0 1 / 0
2.2.1 1 / 0
2.2.0 1 / 0
2.1.0 1 / 0
2.0.0 1 / 0

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.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.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. Consider requesting the maintainer enable provenance via CI/CD.