The Dependency Crusade
Audit every package. Evict the unworthy. The forge-temple's supply lines must be PURE.
/church:dep-crusade
"If a package does not earn its place in the holy dependency tree, it gets EXCOMMUNICATED. Every module is guilty until proven worthy of the Machine God's forge."
— Battle Cry of the Tech-Priests
The Dependency Crusade subjects every package in your manifest to the rigorous trial of an Inquisitorial audit. Four squads scan for vulnerabilities, phantom dependencies, unused packages, and bloat — purging the unworthy with extreme prejudice.
How the Crusade Operates
The sacred operational sequence, as prescribed by the Fabricator-General.
Reconnaissance
The dependency manifest is fed into the sacred cogitator for analysis.
Squad Formation
Four specialist cells receive their hunting parameters.
Parallel Deployment
All squads scan the dependency tree simultaneously.
Synthesis & Triage
Results are merged and prioritized by threat severity.
Master Remediation
The Fabricator-General prescribes the purge sequence.
Victory Report
The supply chain is clean. Only the worthy remain.
The Sacred Laws
The holy laws this crusade enforces. Break them and face the Omnissiah's wrath.
Every dependency must JUSTIFY its existence before the tribunal. 'It was convenient' is not justification — it is SLOTH, the favored sin of the heretek.
Zero known vulnerabilities. A vulnerable dependency is an open gateway for the Dark Mechanicum.
No phantom dependencies. If it is not declared in package.json, it does not EXIST in the sacred manifest.
No duplicates. Two versions of the same package is a schism in the Machine Spirit.
Build tools and runtime tools shall be SEPARATED like the forge and the battlefield.
The Holy Squad
The specialist Tech-Priest agents deployed during this crusade. Each carries only the doctrine they need.