Plugin

indian-company-drafting

For every company-law litigator, insolvency professional, and corporate counsel practising before India's company-law tribunals — every National Company Law Tribunal bench across India and the National Company Law Appellate Tribunal (Principal Bench and Chennai Bench) — this open-source Claude Code plugin standardises Companies Act and IBC drafting. Case-config-aware: forum, share-capital structure, board composition, alleged-oppression acts, scheme terms, capital-reduction arithmetic, strike-off history, investigation grounds, operational-debt particulars, corporate-applicant financial distress, and the NCLT order under appeal are user-supplied. Battle-tested for Sections 241 / 242 / 244 (oppression and mismanagement), Section 245 (class action), Sections 230-232 (compromise / arrangement / amalgamation / scheme), Section 66 (reduction of share capital), Section 252 (revival of a struck-off company), Section 213 (investigation into the affairs of a company), IBC Section 9 (operational-creditor CIRP application), IBC Section 10 (corporate-applicant self-initiation), Companies Act Section 421 (NCLAT appeal from NCLT order), and IBC Section 61 (NCLAT appeal from NCLT order under the IBC). Six-agent drafting pipeline + shared company drafting base with the Companies Act 2013, IBC 2016, NCLT Rules 2016, NCLAT Rules 2016, IBBI Regulations, Secretarial Standards SS-1 / SS-2, Companies (Compromises, Arrangements and Amalgamations) Rules 2016, Companies (Inspection, Investigation and Inquiry) Rules 2014, BNSS 2023, and BSA 2023 encoded. Companies Act 1956 → 2013 transition discipline encoded in the Verifier. The finished product is a Tribunal-ready petition or appeal the chamber can lodge at the NCLT or NCLAT Registry the same day.

• Published source
• Repository

Analysed

11 October 2026

Last observed

13 October 2026

What the code does

What does this mean?

These are capabilities our static analysis found in the latest published version. They describe what the code can do, not whether it is malicious: many tools need shell access or the network to do their job. Use them to decide what to check before installing.

Static analysis found none of the capabilities we track, such as shell commands, network requests or file writes, in the latest version.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.