← Home

lodash.without

npm Repository Homepage

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

20
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-modularizedwithout

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 normal lodash project consolidation, not a takeover. ai
publish-pattern new-deps-added AI (publish-pattern): All new deps are lodash sub-modules from the same ecosystem, consistent with the v4 rewrite refactoring pattern. ai
source-diff source-size-tripled AI (source-diff): Size increase reflects lodash v4 rewrite and dependency restructuring; no obfuscation or payload indicators present. ai

Versions (showing 20 of 20)

Version Deps Published
4.4.0 0 / 0
4.3.0 0 / 0
4.2.0 2 / 0
4.1.2 2 / 0
4.1.1 2 / 0
4.1.0 2 / 0
4.0.2 6 / 0
4.0.1 6 / 0
4.0.0 6 / 0
3.2.1 2 / 0
3.2.0 2 / 0
3.1.0 4 / 0
3.0.0 2 / 0
2.4.1 2 / 0
2.4.0 2 / 0
2.3.0 2 / 0
2.2.1 1 / 0
2.2.0 1 / 0
2.1.0 1 / 0
2.0.0 1 / 0

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

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

1 finding
LOW No provenance attestation provenance

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

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