mortice
Isomorphic read/write lock that works in single processes, node clusters and web workers
mortice@3.3.1 was published on 2025-06-05. Its manifest declares 3 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.
All mortice versions · Permanent reference to 3.3.1
Package specifications
| Version | 3.3.1 |
|---|---|
| License declaration | Apache-2.0 OR MIT |
| Published | 2025-06-05T10:02:41.309Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 380.28 KiB |
| Published file count | 65 |
| Package type | module |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 9 |
| Repository forks | 7 |
Install mortice 3.3.1
npm install mortice@3.3.1 pnpm add mortice@3.3.1 yarn add mortice@3.3.1
Runtime dependencies
- abort-error ^1.0.0
- it-queue ^1.1.0
- main-event ^1.0.0
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.
- abort-error@1.0.2 — direct
- it-pushable@3.2.4 — indirect
- it-queue@1.1.4 — direct
- main-event@1.0.5 — direct
- p-defer@4.0.1 — indirect
- race-event@1.6.1 — indirect
- race-signal@2.0.2 — 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.
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Code-Review | 0/10 — Found 0/27 approved changesets -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| 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 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/mortice/3.3.1 — retrieved 2026-10-29T11:26:49.536Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/systems/npm/packages/mortice/versions/3.3.1:dependencies — retrieved 2026-10-29T10:30:56.396Z
- https://api.deps.dev/v3/systems/npm/packages/mortice/versions/3.3.1 — retrieved 2026-10-29T10:30:56.373Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fachingbrain%2Fmortice — retrieved 2026-10-29T10:30:57.062Z