registry / monomind / 2.24.8

monomind@2.24.8

Open-source CLI extension for Claude Code, OpenCode, Antigravity, Kimi Code, and Codex. Adds an MCP server with a codebase knowledge graph, persistent memory, multi-agent coordination, and reusable slash commands. Apache 2.0 licensed. See https://github.c

AI Security Review

scanned 3d ago · by lpm-firewall-ai

The inspected postinstall is a narrowly scoped metadata cleanup, and the executable entrypoint delegates to the package's declared CLI dependency. The README contains product security disclosures but no review-directed instruction was found in the inspected excerpts.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

The cleanup runs during npm postinstall; the CLI dependency is imported when the `monomind` command starts.

Impact

The cleanup removes matching metadata files within that directory. No confirmed attack effect or unrelated account, credential, or agent-setting action was found.

Mechanism

The cleanup searches the package's relative `node_modules` directory for `._*` files on non-Windows systems. The CLI resolves and imports `@monoes/monomindcli`.

AI rationale

Decision evidence

public snapshot

AI called this Clean at 91.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The postinstall runs only outside Windows and removes `._*` metadata files beneath its relative `node_modules` directory; it does not specify a network request or consumer-project-wide write.
The README describes local state storage and discloses that AI tools send prompts and code to their model providers.
The CLI shim identifies the first-party `@monoes/monomindcli` dependency and imports its resolved CLI entrypoint.

Evidence against

Behavioral surface

Source

DynamicRequireFilesystem

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 2.04 KB of source

Source & flagged code

8 flagged

package.jsonView file

Lines 64-104json

64 "autonomous-agents",

65 "hooks",

66 "antigravity",

67 "agy",

68 "gemini"

69 ],

70 "author": {

71 "name": "nokhodian",

72 "email": "nokhodian@gmail.com",

73 "url": "https://github.com/nokhodian"

74 },

75 "license": "Apache-2.0",

76 "publishConfig": {

77 "access": "public",

78 "tag": "latest"

79 },

80 "volta": {

81 "node": "22.23.2"

82 },

83 "scripts": {

84 "postinstall": "node -e \"if(process.platform!=='win32'){try{require('child_process').execSync('find node_modules -name ._* -delete 2>/dev/null',{stdio:'ignore'})}catch{}}\"",

Critical

Red Install Lifecycle Script

Install-time lifecycle script matches a deterministic static-gate block pattern.

package.jsonView on unpkg · L84

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L84

85 "dev": "cd packages/@monomind/cli && tsx watch src/index.ts",

Low

Suspicious Lifecycle Evidence

The postinstall runs only outside Windows and removes `._*` metadata files beneath its relative `node_modules` directory; it does not specify a network request or consumer-project-wide write.

package.jsonView on unpkg · L84

86 "build": "pnpm -r run build",

87 "build:ts": "cd packages/@monomind/cli && npm run build",

88 "typecheck": "tsc --noEmit -p tsconfig.json",

89 "check:versions": "node scripts/check-publish-versions.mjs && node scripts/check-package-bumps.mjs && node scripts/check-workspace-protocol.mjs && node scripts/check-overrides-source.mjs",

90 "docs:counts": "node scripts/generate-doc-counts.mjs",

91 "docs:counts:check": "node scripts/generate-doc-counts.mjs --check",

92 "docs:refs:check": "node scripts/check-doc-refs.mjs",

93 "sync:claude-trees": "node scripts/sync-claude-trees.mjs",

94 "sync:claude-trees:check": "node scripts/sync-claude-trees.mjs --check",

95 "setup:merge-drivers": "git config merge.monomind-changelog.name \"monomind CHANGELOG.md: keep released sections, move new entries to Unreleased\" && git config merge.monomind-changelog.driver \"node scripts/merge-changelog.mjs %O %A %B\"",

96 "test": "vitest",

97 "test:all": "vitest --config vitest.workspace.ts",

98 "test:run": "vitest run",

99 "test:all:run": "vitest run --config vitest.workspace.ts",

100 "test:ui": "vitest --ui",

101 "test:security": "vitest run tests/security/",

102 "test:semantic-eval": "node --test tests/memory/cognee-port-eval.test.mjs",

103 "test:coverage": "vitest run --coverage",

104 "verify": "pnpm run build && pnpm run typecheck && pnpm run lint && pnpm run docs:refs:check && pnpm run lint:agent-refs && pnpm run lint:tool-refs && pnpm run sync:claude-trees:check && pnpm run test:all:run && pnpm --filter @monoes/monobrowse test && pnpm --filter @monoes/monodesign test && pnpm --filter monofence-ai test",

README.mdView file

Lines 90-130markdown

90```bash

91codex login

92monomind init --codex

93```

95This emits a project-scoped `.codex/config.toml` that registers Monomind's MCP

96server, plus `AGENTS.md` with Codex-specific guidance. Codex must trust the

97project before it loads project-scoped configuration. To run persistent

bin/cli.jsView file

Lines 1-63javascript

1#!/usr/bin/env node

2/**

3 * monomind — umbrella entry point.

4 *

5 * This package ships NO code of its own. It is a thin shim that depends on

6 * @monoes/monomindcli (the real CLI) and hands off to its bin. Publishing the

7 * CLI payload from both packages is what caused the ~27MB double-publish and

8 * the two-file lockstep version bump; do not reintroduce it.

9 */

10import { createRequire } from

Source & flagged code

8 flagged · loading source

package.jsonView file

•scripts.postinstall = node -e "if(process.platform!=='win32'){try{require('child_process').execSync('find node_modules -name ._* -delete 2>/dev/null',{stdio:'ignore'})}catch{}}"

Critical

Red Install Lifecycle Script

Install-time lifecycle script matches a deterministic static-gate block pattern.

package.jsonView on unpkg

•scripts.postinstall = node -e "if(process.platform!=='win32'){try{require('child_process').execSync('find node_modules -name ._* -delete 2>/dev/null',{stdio:'ignore'})}catch{}}"

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

84"postinstall": "node -e \"if(process.platform!=='win32'){try{require('child_process').execSync('find node_modules -name ._* -delete 2>/dev/null',{stdio:'ignore'})}catch{}}\"",

Low

Suspicious Lifecycle Evidence

The postinstall runs only outside Windows and removes `._*` metadata files beneath its relative `node_modules` directory; it does not specify a network request or consumer-project-wide write.

package.jsonView on unpkg · L84

Findings

1 Critical2 High2 Medium6 Low

CriticalRed Install Lifecycle Scriptpackage.json

HighInstall Time Lifecycle Scriptspackage.json

HighAi Reviewer ManipulationREADME.md

MediumDynamic Requirebin/cli.js

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowSuspicious Lifecycle Evidencepackage.json

LowAi Review EvidenceREADME.md

LowSuspicious Dependency Evidencebin/cli.js

Affected versions and remediation

This report applies to monomind@2.24.8.

See all versions of monomind for other recorded verdicts.

Review the evidence and your use of monomind@2.24.8 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-10-20 07:22:32.770Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.