y-lock
Promise-based semaphore implementation
y-lock@5.0.0 was published on 2017-08-28. 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 y-lock versions · Permanent reference to 5.0.0
Package specifications
| Version | 5.0.0 |
|---|---|
| License declaration | Apache-2.0 |
| Published | 2017-08-28T20:47:55.806Z |
| 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 | main.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 0 |
| Repository forks | 0 |
Install y-lock 5.0.0
npm install y-lock@5.0.0 pnpm add y-lock@5.0.0 yarn add y-lock@5.0.0
Runtime dependencies
- y-resolver ^11.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.
- detacher@2.0.11 — indirect
- greens@1.0.6 — indirect
- u-proto@7.1.9 — indirect
- y-resolver@11.0.1 — direct
- y-setter@8.0.1 — indirect
- y-timers@1.1.11 — indirect
- y-walk@10.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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| SAST | 0/10 — no SAST tool detected |
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
| Maintained | 0/10 — project is archived |
| 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/y-lock/5.0.0 — retrieved 2026-10-29T13:20:55.545Z
- https://api.deps.dev/v3/systems/npm/packages/y-lock/versions/5.0.0 — retrieved 2026-10-29T13:20:56.049Z
- https://api.deps.dev/v3/systems/npm/packages/y-lock/versions/5.0.0:dependencies — retrieved 2026-10-29T13:20:56.089Z
- https://api.deps.dev/v3/projects/github.com%2Fmanvalls%2Fy-lock — retrieved 2026-10-29T13:20:56.224Z