Clearance — Dependency Licences & Obligations

Clearance — Dependency Licences & Obligations — a premium, 100% offline digital tool by Aceplore. Runs entirely in your browser: no accounts, no subscriptions, your data never leaves your device.

A private, offline register of the licences your dependencies carry — the obligations your distribution mode actually triggers, the path a copyleft package takes to your product, and a NOTICE file that lists its own gaps. 35 tools in one, and it refuses to guess.

35 built-in tools in one app. A dependency inventory with version, ecosystem, linkage and whether you modified it, and a direct-against-transitive view, since the second group is where the surprises live; a licence register with family, obligations and patent position as YOU recorded them, a families split, and an UNKNOWN list — the most important view in the app, because an unrecorded licence is not a permissive one and is never netted out of a percentage; obligations and their TRIGGERS across distribute, modify, network and always; products with their DISTRIBUTION MODE, which changes everything about what is triggered, a usage map, and an APPLICABLE view giving the obligations actually fired for a product given its distribution mode and each dependency's linkage; a copyleft view, a REACH view drawing the propagation PATH from a copyleft dependency through intermediate packages to a product, a linkage view explaining why static, dynamic, service and build-only are treated differently, and a build-only view separating what never ships; the compatibility rules YOU configured and a licence-against-licence matrix showing unconfigured pairs as REVIEW and never as compatible; a per-product check listing every dependency, verdict and reason, findings, a generated NOTICE file listing dependencies whose attribution text is missing as GAPS rather than omitting them, a modified-dependency view, a patents view and a full printable inventory; plus CSV exports, a JSON backup and a Method page stating exactly how verdicts are reached and what their limits are.

Unconfigured pairs. Never compatible — the app does not guess on your behalf.

Triggers. What actually fires, and which trigger fired it.

What's included:

• Clearance.html
• Quick-Start-Guide.html
• How-To-Use-Guide.html
• README.txt
• LICENSE.txt

Includes a personalized welcome wizard, an interactive guided tour, a ⌘K command palette, light/dark themes with 8 accents, and one-click JSON backup & restore.

Clearance is a planning, costing and record-keeping tool for software and infrastructure work. Every figure it reports is computed by a stated formula from the numbers YOU enter, and every figure carries its UNIT, because a millisecond, a byte, a request, a vCPU-hour and a user-minute are different quantities and confusing them is the classic failure in this field. Byte and month conventions are settings and are printed beside the figures they produced — 1 KB = 1,000 bytes and 1 KiB = 1,024 bytes are both correct and they disagree. Where something is consumed against an allowance, the consumed amount, the remaining amount floored at zero and the overage are reported separately, because a negative remaining renders as headroom and that is how an outage gets missed. Where a figure rests on an assumption — a hit ratio, a growth rate, a base event rate, an hourly price — it is labelled an assumption at the point of use and is yours to change. It runs entirely in your browser with no network access of any kind: it cannot reach a server, a registry or a cloud account, and it reports only what you recorded. It does not predict an outcome and is not a guarantee of uptime, of a deploy, of a bill, of compliance or of security posture, and nothing in it is legal advice.