lodash.intersection
The lodash method `_.intersection` 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:lodash._baseintersection | AI (dependencies): lodash._baseintersection is a lodash internal module from the same author (jdalton); standard modularized lodash dependency pattern, not a real risk. | ai | |
| provenance | no-provenance | AI (provenance): Long-established lodash modular package published by jdalton before Sigstore provenance was available. Not a meaningful risk signal for this package. | ai |
Versions (showing 22 of 22)
| 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.0 | 4 / 0 | |
| 3.1.0 | 3 / 0 | |
| 3.0.3 | 5 / 0 | |
| 3.0.2 | 5 / 0 | |
| 3.0.1 | 5 / 0 | |
| 3.0.0 | 5 / 0 | |
| 2.4.1 | 9 / 0 | |
| 2.4.0 | 9 / 0 | |
| 2.3.0 | 7 / 0 | |
| 2.2.1 | 7 / 0 | |
| 2.2.0 | 7 / 0 | |
| 2.1.0 | 7 / 0 | |
| 2.0.0 | 7 / 0 |
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package 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. Consider requesting the maintainer enable provenance via CI/CD.