← Home

lodash.toarray

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

22
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-modularizedtoarray

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): Historical lodash maintainer consolidation under jdalton (original author); not a takeover signal for this package. ai
publish-pattern new-deps-added AI (publish-pattern): lodash._arraymap is a standard lodash internal utility; dependency swap is consistent with lodash 4.x modularized refactor. ai
source-diff source-size-tripled AI (source-diff): Size increase reflects lodash 3.x → 4.x major version refactor of modularized packages, not injected payload. ai

Versions (showing 22 of 22)

Version Deps Published
4.4.0 0 / 0
4.3.0 0 / 0
4.2.4 2 / 0
4.2.3 2 / 0
4.2.2 2 / 0
4.2.1 2 / 0
4.2.0 2 / 0
4.1.1 3 / 0
4.1.0 3 / 0
4.0.2 2 / 0
4.0.1 2 / 0
4.0.0 2 / 0
3.0.2 3 / 0
3.0.1 3 / 0
3.0.0 3 / 0
2.4.1 3 / 0
2.4.0 3 / 0
2.3.0 3 / 0
2.2.1 3 / 0
2.2.0 3 / 0
2.1.0 3 / 0
2.0.0 3 / 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.4

1 finding
LOW No provenance attestation provenance

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

v4.2.3

1 finding
LOW No provenance attestation provenance

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

v4.2.2

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

1 finding
LOW No provenance attestation provenance

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

v3.0.1

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.