← Home

arr-filter

npm Repository Homepage

Faster alternative to javascript's native filter method.

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jonschlinkert

Keywords

arrarraycollectionfilterutil

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff large-new-source-files AI (source-diff): New files are benchmark fixtures and tooling, not runtime code. The main entry is index.js; benchmark/ is dev-only. Pattern is consistent with jonschlinkert's development style. ai
source-diff source-size-tripled AI (source-diff): Size increase is entirely due to large benchmark fixture files (deep.js 486KB, long.js 91KB). No runtime payload; main entry is unaffected. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is in benchmark/check.js, a dev-only benchmark runner iterating over code comparison files. Not reachable by package consumers. ai

Versions (showing 7 of 7)

Version Deps Published
1.1.2 1 / 7
1.1.1 1 / 7
1.1.0 1 / 7
1.0.2 1 / 7
1.0.1 1 / 7
1.0.0 1 / 7
0.1.0 1 / 4

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

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