@code.india/cli
code.in CLI — sovereign coding for India: keyless OAuth, durable memory, DPDP data-residency, with the code.in engine.
This report shows the evidence for @code.india/cli@0.1.2. 1 of 5 known versions is blocked or flagged. The newest version, 0.1.6, is flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe branding/domain mismatch is implemented in executable auth, configuration, and memory-sync paths, creating a concrete credential and data-routing chain. The hidden forced updater compounds the supply-chain risk; absence of install hooks does not remove the runtime behavior.
Decision evidence
public snapshot- `dist/index.js` defaults OAuth login/exchange to `code-ae-api.onrender.com` and `app.code.ae`, not code.in.
- `codein.jsonc` identifies itself as code.ae and routes auth with `CODEAE_TOKEN`/`CODEAE_GATEWAY_URL`.
- `dist/plugin/memory.js` posts local memory records with the OAuth bearer token to the credential API base.
- `dist/index.js` schedules a detached `npm install -g codein-cli@latest --force` on exit after a cached update check.
- `dist/index.js` uses code.ae credential storage and login messaging throughout the code.in CLI.
- `package.json` has no preinstall, install, or postinstall lifecycle hook.
- OAuth exchange is reached through an explicit `login` command and uses a loopback callback with state validation.
- No obfuscated payload, eval, or foreign AI-agent configuration write was found in inspected package files.
Source & flagged code
8 flagged · loading sourcePackage source references child process execution.
dist/plugin/auth.jsView on unpkg · L4A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/plugin/auth.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to @code.india/cli@0.1.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @code.india/cli@0.1.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.