agentinel 0.0.10 → 1.0.0

package/README.md

@@ -4,6 +4,7 @@
   [![npm version](https://img.shields.io/npm/v/agentinel.svg?style=flat-square)](https://www.npmjs.com/package/agentinel)
   [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg?style=flat-square)](LICENSE)
   [![Node.js CI](https://img.shields.io/github/actions/workflow/status/aman-janwani/agentinel/publish.yml?style=flat-square)](https://github.com/aman-janwani/agentinel/actions)
+  [![Tested On](https://img.shields.io/badge/Tested_On-macOS_%7C_Linux_%7C_Windows-success?style=flat-square)](#)
 </div>
 
 <br />
@@ -34,6 +35,7 @@ Every other tool in this space guards your terminal. **Agentinel guards your age
 - **Known Malware:** Bundles a local OSV database of 216,000+ confirmed malicious packages.
 - **Zero False Positives on Popular Packages:** Tested against the top 100 npm packages.
 - **Heuristic Scanning:** Flags npm takedowns, packages under 30 days old with < 1k downloads (slopsquatting), publisher drift, and non-existent hallucinated names.
+- **Cross-Platform Compatibility:** Fully tested and natively supported across macOS, Linux, and Windows.
 - **Fails Open:** Designed so that if it crashes or can't reach the registry, it fails open. It will never permanently wedge your terminal or block your work.
 
 ---
@@ -119,17 +121,31 @@ How do we stack up against traditional commercial security scanners?
 
 ---
 
-## ⚙️ Configuration (Warn vs. Block)
+## ⚙️ Modes: warn vs strict
 
-By default, Agentinel runs in **Warn Mode**. It alerts you (and the agent) but gets out of the way. 
-To strictly block bad packages, change your `.agentinel.json` file to strict mode:
+Agentinel supports two operating modes, controlled by the `mode` field. You can switch between them using `npx asen mode <warn|strict>`.
 
+### warn (default)
+Agentinel surfaces a warning in the agent output but does not block the install. The agent decides whether to proceed.
+
+`.agentinel.json`
 ```json
 {
-  "mode": "strict",
-  "allowlist": {}
+  "mode": "warn"
 }
 ```
+*Best for teams migrating to Agentinel gradually or using agents in read-heavy workflows.*
+
+### strict
+Agentinel hard-blocks the install and returns an error payload to the agent. The install never reaches npm.
+
+`.agentinel.json`
+```json
+{
+  "mode": "strict"
+}
+```
+*Recommended for production repos, CI pipelines, and any project with autonomous agentic access.*
 
 ---
 
@@ -137,31 +153,40 @@ To strictly block bad packages, change your `.agentinel.json` file to strict mod
 
 Here are all the commands you can run via `npx asen <command>`:
 
-### `npx asen init`
+### `npx asen init [--shim]`
 Wires up agent hooks and git hooks in the current repo.
 ```bash
 $ npx asen init
-✅ Wired up pre-commit git hook.
-✅ Wired up Claude Code PreToolUse hook.
+wrote .agentinel.json
+registered the Claude Code PreToolUse hook in .claude/settings.json
+installed the git pre-commit hook in .git/hooks
+
+agentinel is set up. New npm packages will be checked before they land.
+Default mode is warn. Set "mode": "strict" in .agentinel.json to block instead.
 ```
 
-### `npx asen init --shim`
-Wires up hooks AND installs the global PATH shim for human terminal protection.
+When used with `--shim`, it wires up hooks AND installs the global PATH shim for human terminal protection.
 ```bash
 $ npx asen init --shim
-✅ Shim installed. Native terminal npm commands are now guarded.
-✅ Wired up pre-commit git hook.
+wrote .agentinel.json
+registered the Claude Code PreToolUse hook in .claude/settings.json
+installed the git pre-commit hook in .git/hooks
+wrote shims for npm, npx, pnpm, yarn, bun in /Users/user/.agentinel/bin
+added the shims to PATH in /Users/user/.zshrc
+Mode is warn, so a risky package typed at the terminal will be reported, not blocked.
+Open a new terminal, or run \`asen unshim\` to undo this.
+
+agentinel is set up. New npm packages will be checked before they land.
+Default mode is warn. Set "mode": "strict" in .agentinel.json to block instead.
 ```
 
-### `npx asen check`
+### `npx asen check [pkg...]`
 Scans the currently staged dependencies in your lockfile. Exits non-zero if flagged (great for CI/CD pipelines).
 ```bash
 $ npx asen check
-Scanning staged dependencies...
-✅ All 142 staged packages passed security checks.
+checked 142 package(s), nothing suspicious
 ```
 
-### `npx asen check <package-name>`
 Scans a specific package instantly without installing it.
 ```bash
 $ npx asen check react-router-v7-fake
@@ -169,18 +194,26 @@ $ npx asen check react-router-v7-fake
 This matches the profile of a slopsquatting or malicious package.
 ```
 
-### `npx asen allow <package-name> --reason "why"`
+### `npx asen allow <pkg> --reason "..."`
 Adds a package to the allowlist in `.agentinel.json` with a required reason. This provides an audited trail for your team.
 ```bash
 $ npx asen allow my-internal-pkg --reason "Internal company package not on public npm"
-✅ Added my-internal-pkg to .agentinel.json allowlist.
+allowlisted my-internal-pkg in .agentinel.json
+```
+
+### `npx asen mode <warn|strict>`
+Switches Agentinel's operating mode in the `.agentinel.json` file.
+```bash
+$ npx asen mode strict
+set mode to strict in .agentinel.json
 ```
 
 ### `npx asen unshim`
 Removes the global PATH shim.
 ```bash
 $ npx asen unshim
-✅ Shim removed. Normal npm path restored.
+removed /Users/user/.agentinel/bin
+removed the PATH line from /Users/user/.zshrc
 ```
 
 ---

package/dist/asen.js

@@ -102,7 +102,21 @@ import { join } from "path";
 // src/config/schema.ts
 var CONFIG_FILENAME = ".agentinel.json";
 function defaultConfig() {
-  return { mode: "warn", allow: [] };
+  return {
+    mode: "warn",
+    allow: [
+      {
+        name: "asen",
+        reason: "Agentinel CLI tool",
+        date: (/* @__PURE__ */ new Date()).toISOString().substring(0, 10)
+      },
+      {
+        name: "agentinel",
+        reason: "Agentinel package",
+        date: (/* @__PURE__ */ new Date()).toISOString().substring(0, 10)
+      }
+    ]
+  };
 }
 function parseConfig(raw, warn2 = () => {
 }) {
@@ -1464,6 +1478,24 @@ function asRecord2(value) {
   return typeof value === "object" && value !== null ? value : null;
 }
 
+// src/commands/mode.ts
+function runMode(targetMode) {
+  if (targetMode !== "warn" && targetMode !== "strict") {
+    console.error("usage: asen mode <warn|strict>");
+    return 1;
+  }
+  const repoRoot = repoRootOrCwd();
+  const config = loadConfig(repoRoot);
+  if (config.mode === targetMode) {
+    console.log(`mode is already ${targetMode}`);
+    return 0;
+  }
+  config.mode = targetMode;
+  saveConfig(repoRoot, config);
+  console.log(`set mode to ${targetMode} in .agentinel.json`);
+  return 0;
+}
+
 // src/hooks/claude-code.ts
 import { existsSync as existsSync6 } from "fs";
 import { join as join6 } from "path";
@@ -1769,6 +1801,7 @@ var USAGE = `asen, a guard for AI coding agent workflows
   asen init [--shim]                 set up the hooks and config in this repo
   asen check [pkg...]                check staged dependencies, or specific packages
   asen allow <pkg> --reason "..."    allowlist a flagged package, with a logged reason
+  asen mode <warn|strict>            switch Agentinel's operating mode
   asen unshim                        remove the PATH shims that --shim installed
 `;
 async function main(argv2) {
@@ -1780,6 +1813,8 @@ async function main(argv2) {
       return runCheck(positionals(rest));
     case "allow":
       return runAllow(positionals(rest)[0], readFlag(rest, "--reason"));
+    case "mode":
+      return runMode(positionals(rest)[0]);
     case "unshim":
       return removeShim();
     // Not documented in the usage text on purpose. These are what the installed hooks call.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentinel",
-  "version": "0.0.10",
+  "version": "1.0.0",
   "description": "Catches AI hallucinated npm packages before an agent installs them",
   "license": "MIT",
   "author": "Aman Janwani",