sver-compat
Simple Semver and SemverRange classes
sver-compat@1.5.0 was published on 2017-08-18. Its manifest declares 2 runtime dependencies 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 sver-compat versions · Permanent reference to 1.5.0
Package specifications
| Version | 1.5.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-08-18T21:40:57.813Z |
| Node.js requirement | Not declared |
| 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 | sver.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 9 |
| Repository stars | 2 |
| Repository forks | 0 |
Install sver-compat 1.5.0
npm install sver-compat@1.5.0 pnpm add sver-compat@1.5.0 yarn add sver-compat@1.5.0
Runtime dependencies
- es6-iterator ^2.0.1
- es6-symbol ^3.1.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.
- d@1.0.2 — indirect
- es5-ext@0.10.64 — indirect
- es6-iterator@2.0.3 — direct
- es6-symbol@3.1.4 — direct
- esniff@2.0.1 — indirect
- event-emitter@0.3.5 — indirect
- ext@1.7.0 — indirect
- next-tick@1.1.0 — indirect
- type@2.7.3 — 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.
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Security-Policy | 10/10 — security policy file detected |
| 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 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/sver-compat/1.5.0 — retrieved 2026-10-29T09:02:18.955Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/systems/npm/packages/sver-compat/versions/1.5.0:dependencies — retrieved 2026-10-29T09:02:18.937Z
- https://api.deps.dev/v3/systems/npm/packages/sver-compat/versions/1.5.0 — retrieved 2026-10-29T09:02:18.911Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fphated%2Fsver-compat — retrieved 2026-10-29T09:02:19.784Z