array-includes 1.0.4
A spec-compliant `Array.prototype.includes` shim/polyfill/replacement that works as far down as ES3.
array-includes@1.0.4 was published on 2015-01-11. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.4.
All array-includes versions · Permanent reference to 1.0.4 · Latest release
Package specifications
| Version | 1.0.4 |
|---|---|
| License declaration | MIT |
| Published | 2015-01-11T03:19:02.714Z |
| Node.js requirement | >= 0.4 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 43 |
| Repository forks | 12 |
Install array-includes 1.0.4
npm install array-includes@1.0.4 pnpm add array-includes@1.0.4 yarn add array-includes@1.0.4
Runtime dependencies
- es-abstract ~1.0.0
- define-properties ~1.0.1
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- define-properties@1.0.2 — direct
- es-abstract@1.0.1 — direct
- foreach@2.0.6 — indirect
- is-callable@1.0.4 — indirect
- object-keys@1.1.1 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 4/10 — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4 |
|---|---|
| Code-Review | 0/10 — Found 1/30 approved changesets -- score normalized to 0 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | 10/10 — security policy file detected |
Evidence and freshness
- https://registry.npmjs.org/array-includes/1.0.4 — retrieved 2026-10-29T15:20:13.257Z
- https://api.deps.dev/v3/projects/github.com%2Fes-shims%2Farray-includes — retrieved 2026-10-29T12:12:33.078Z
- https://api.deps.dev/v3/systems/npm/packages/array-includes/versions/1.0.4 — retrieved 2026-10-29T15:20:13.802Z
- https://api.deps.dev/v3/systems/npm/packages/array-includes/versions/1.0.4:dependencies — retrieved 2026-10-29T15:20:13.815Z