stable
A stable array sort for JavaScript
stable@0.1.8 was published on 2018-04-25. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
Deprecated: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
All stable versions · Permanent reference to 0.1.8
Package specifications
| Version | 0.1.8 |
|---|---|
| License declaration | MIT |
| Published | 2018-04-25T14:41:39.506Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 0 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 8.21 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./stable.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 0 |
| Repository stars | 80 |
| Repository forks | 12 |
Install stable 0.1.8
npm install stable@0.1.8 pnpm add stable@0.1.8 yarn add stable@0.1.8
Runtime dependencies
- None declared
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.
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 — project is archived |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 1/10 — Found 2/17 approved changesets -- score normalized to 1 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| License | 0/10 — license file not detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/stable/0.1.8 — retrieved 2026-10-29T09:28:59.820Z
- https://api.deps.dev/v3/systems/npm/packages/stable/versions/0.1.8 — retrieved 2026-10-29T09:29:00.329Z
- https://api.deps.dev/v3/systems/npm/packages/stable/versions/0.1.8:dependencies — retrieved 2026-10-29T09:29:00.377Z
- https://api.deps.dev/v3/projects/github.com%2FTwo-Screen%2Fstable — retrieved 2026-10-29T09:29:00.548Z