array.prototype.find MIT 15 versions

array.prototype.find

npm Repository Homepage

Array.prototype.find ES6 polyfill.

15

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

paulmillrljharb

Keywords

Array.prototype.findfindes6ecmascript 6polyfill

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from paulmillr to ljharb occurred in 2016 — a long-settled, legitimate maintainer transition. ljharb is a highly trusted npm publisher with 4000+ approved packages.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): ljharb was added as maintainer in 2016 as part of a legitimate transition. This is a historical, well-known change in the es-shims ecosystem.	ai	2026/04/24
email-domain	unclaimed-email:http://paulmillr.com	AI (email-domain): The author field uses a URL (http://paulmillr.com) not an email address. paulmillr.com is Paul Miller's active personal site; this is a false positive from the analyzer misinterpreting the URL field.	ai	2026/04/23
publish-pattern	new-deps-added	AI (publish-pattern): es-object-atoms is a legitimate es-shims ecosystem package maintained by ljharb, the same publisher. Routine dependency addition consistent with this package's ecosystem.	ai	2026/04/23

Versions (showing 15 of 15)

Version	Deps	Published
2.2.3	5 / 12	2024-03-19
2.2.2	4 / 12	2023-08-27
2.2.1	4 / 11	2022-11-02
2.2.0	4 / 10	2022-04-12
2.1.2	3 / 8	2021-10-01
2.1.1	2 / 6	2020-02-24
2.1.0	2 / 5	2019-05-23
2.0.4	2 / 5	2017-03-30
2.0.3	2 / 5	2017-01-24
2.0.2	2 / 5	2017-01-24
2.0.1	2 / 5	2016-12-13
2.0.0	2 / 3	2016-01-31
1.0.0	0 / 2	2014-08-14
0.1.1	0 / 0	2014-03-24
0.1.0	0 / 0	2013-12-20

v2.2.3

2 findings

HIGH Unclaimed maintainer email domain: http://paulmillr.com email-domain

Maintainer email 'http://paulmillr.com' uses domain 'http://paulmillr.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

2 findings

HIGH Publisher changed: paulmillr → ljharb (on 2017-01-24) provenance

This version was published by a different npm account than previous versions on 2017-01-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.2

2 findings

HIGH Publisher changed: paulmillr → ljharb (on 2017-01-24) provenance

This version was published by a different npm account than previous versions on 2017-01-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.1

2 findings

HIGH Publisher changed: paulmillr → ljharb (on 2016-12-13) provenance

This version was published by a different npm account than previous versions on 2016-12-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.0

2 findings

HIGH Publisher changed: paulmillr → ljharb (on 2016-01-31) provenance

This version was published by a different npm account than previous versions on 2016-01-31. This could indicate a legitimate maintainer transition or an account compromise.

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.