array-to-error 1.1.0
Create an error from an array of error messages
array-to-error@1.1.0 was published on 2016-06-08. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All array-to-error versions · Permanent reference to 1.1.0 · Latest release
Package specifications
| Version | 1.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2016-06-08T08:30:02.871Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| 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 | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 1 |
| Repository forks | 0 |
Install array-to-error 1.1.0
npm install array-to-error@1.1.0 pnpm add array-to-error@1.1.0 yarn add array-to-error@1.1.0
Runtime dependencies
- array-to-sentence ^1.0.4
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.
- array-to-sentence@1.1.0 — direct
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 | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 0/10 — Found 0/19 approved changesets -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/array-to-error/1.1.0 — retrieved 2026-10-29T18:43:45.890Z
- https://api.deps.dev/v3/projects/github.com%2Fshinnn%2Farray-to-error — retrieved 2026-10-29T15:23:12.049Z
- https://api.deps.dev/v3/systems/npm/packages/array-to-error/versions/1.1.0:dependencies — retrieved 2026-10-29T18:43:46.439Z
- https://api.deps.dev/v3/systems/npm/packages/array-to-error/versions/1.1.0 — retrieved 2026-10-29T18:43:46.412Z