Deploom Core is a headless Python engine for planning dependency upgrades in JavaScript/TypeScript projects. It models candidate versions and compatibility requirements, records which declarations the user has authorized to change, and reports what is known, blocked, or still unverified.
Core creates plans. It does not automatically prove that an npm installation, an application's tests, or runtime behavior will succeed.
- Proposes version candidates within selected scope and approved version lines.
- Uses a Z3-backed model for declared compatibility/peer constraints and finite joint choices where supported.
- Distinguishes minimum changes needed for a health objective from newer choices within approved lines.
- Preserves
pinnedversusadvisorytarget authority, unchanged declarations, blockers, deferred work, and missing evidence. - Tracks source/workspace coverage and input identities so stale or partial plans remain visible.
- Checks held npm peer providers and records lockfile changes, including when npm reclassifies a held package from production to development use.
- Supports constrained npm workspace scenarios, but does not claim arbitrary monorepo, lockfile, or runtime correctness from a static assignment.
A Draft proposal is PLANNING_ONLY / NOT_VERIFIED. An accepted lockfile, a clean install, effective dependency providers, project checks, and runtime acceptance are separate results.
Developer / coding agent
│
▼
Deploom MCP
│ structured request / Blueprint
▼
Deploom Core
│ versions, constraints, evidence
▼
Proposed plan → independent npm + project verification
Deploom MCP is the user-facing agent integration and includes a pinned copy of Core in its published wheel. You do not need to install Core separately to run that wheel.
Supported Core Python range: 3.12–3.13 (>=3.12,<3.14). From a clean checkout:
python -m venv .venv
python -m pip install -e .
python dependency_live_roadmap_generator.py --help
python -m unittest discover -s tests -p 'test_required_planner.py' -vUse the interpreter from your virtual environment if python resolves elsewhere. The CI workflow and testing notes describe which tests are covered; a green lightweight suite is not a full migration acceptance.
- MCP integration and pinned Core
- Testing boundary
- Release process
- Architecture/extraction background
- Historical experiments and limitations
| Repository | Purpose |
|---|---|
| deploom-core | Core decision and planning engine |
| deploom-mcp | MCP tools, Blueprint adapter, agent Skill, and authorized evidence workflows |
DepLoom Core and its first-party schemas are licensed under the Apache License 2.0.
Download Core and the matching checksums from GitHub Releases. Run project acceptance on the final dependency tree.
