@hone-ai/cli@1.35.1: Suspicious npm security report (Warn) | LPM Firewall

Loading npm security reports…

@hone-ai/cli@1.35.1: Suspicious npm security report (Warn) | LPM Firewall

Source & flagged code

11 flagged · loading source

package.jsonView file

•scripts.postinstall = echo '\n Hone AI CLI installed successfully.\n Next: run `hone init --token <YOUR_TOKEN>` to configure.\n Docs: https://www.npmjs.com/package/@hone-ai/cli\n'

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•scripts.postinstall = echo '\n Hone AI CLI installed successfully.\n Next: run `hone init --token <YOUR_TOKEN>` to configure.\n Docs: https://www.npmjs.com/package/@hone-ai/cli\n'

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

hone-cli.jsView file

•matchType = previous_version_dangerous_delta matchedPackage = @hone-ai/cli@1.34.0 matchedIdentity = npm:QGhvbmUtYWkvY2xp:1.34.0 similarity = 0.780 summary = stored previous version shares package body but lacks this dangerous source file

Critical

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

hone-cli.jsView on unpkg

25const crypto = require('crypto'); L26: const { execSync } = require('child_process'); L27:

High

Child Process

Package source references child process execution.

hone-cli.jsView on unpkg · L25

8060const probed = spawnSync(plan.probe, { L8061: cwd: process.cwd(), shell: true, encoding: 'utf8', L8062: timeout: 60_000, env: verifyCommandEnv(gitEnv()), stdio: ['ignore', 'pipe', 'pipe'],

High

Shell

Package source references shell execution.

hone-cli.jsView on unpkg · L8060

•Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration. hone-cli.js: baseURL: config.apiUrl, Authorization: `Bearer ${config.token}`, fs.writeFileSync(target, f.content); fs.writeFileSync(pipelineConfigPath, updated); fs.writeFileSync(configPath, result.augmentedConfig); fs.writeFileSync(path.join(agentsDir, `${agent}.agent.md`), data), fs.writeFileSync(path.join(skillDir, 'SKILL.md'), data); write: (data) => fs.writeFileSync(path.join(enterpriseGH, 'copilot-instructions.md'), data),

High

Credential Redirect Persistence

Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.

hone-cli.jsView on unpkg

1303L1304: const installCmd = detected.pkgMgr === 'yarn' ? 'yarn add -D' : detected.pkgMgr === 'pnpm' ? 'pnpm add -D' : 'npm install -D'; L1305: ... L1311: try { L1312: execSync(`${installCmd} ${pkgs.unit.join(' ')}`, { stdio: 'inherit', cwd: repoRoot }); L1313: console.log(` ✓ Unit test framework installed`);

High

Runtime Package Install

Package source invokes a package manager install command at runtime.

hone-cli.jsView on unpkg · L1303

bin/hone-mcp.jsView file

6// detached-ok: top-level entrypoint - the process lifetime IS the await, and no caller exists to observe it L7: require('../mcp-server.js').start().catch((e) => { L8: process.stderr.write(`hone-mcp failed: ${e && e.message ? e.message : String(e)}\n`);

Medium

Dynamic Require

Package source references dynamic require/import behavior.

bin/hone-mcp.jsView on unpkg · L6

lib/hook-templates/pre-push.shView file

•path = lib/hook-templates/pre-push.sh kind = build_helper sizeBytes = 2812 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

lib/hook-templates/pre-push.shView on unpkg

lib/auto-verify.js#virtual:normalized:round1View file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 15

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

lib/auto-verify.js#virtual:normalized:round1View on unpkg

lib/performance-analyzer.jsView file

•matchType = normalized_sha256 matchedPackage = @hone-ai/cli@1.28.0 matchedPath = lib/performance-analyzer.js matchedIdentity = npm:QGhvbmUtYWkvY2xp:1.28.0 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

lib/performance-analyzer.jsView on unpkg

Source & flagged code

11 flagged

package.jsonView file

Lines 4-44json

4 "description": "Hone AI — Enterprise SDLC Pipeline CLI",

5 "main": "hone-cli.js",

6 "bin": {

7 "hone": "./bin/hone.js",

8 "hone-mcp": "./bin/hone-mcp.js"

9 },

10 "files": [

11 "README.md",

12 "bin/",

13 "hone-cli.js",

14 "lib/",

15 "!lib/*.test.js",

16 "schema/",

17 "mcp-server.js"

18 ],

19 "scripts": {

20 "test": "echo \"No tests yet\" && exit 0",

21 "link": "npm link",

22 "sync-server-cli-version": "node scripts/sync-server-cli-version.js",

23 "prepublishOnly": "node scripts/sync-server-cli-version.js",

24 "postinstall": "echo '\\n Hone AI CLI installed successfully.\\n Next: run `hone init --token <YOUR_TOKEN>` to configure.\\n Docs: https://www.npmjs.com/package/@hone-ai/cli\\n'"

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L24

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg · L24

25 },

26 "dependencies": {

27 "@modelcontextprotocol/sdk": "^1.30.0",

28 "ajv": "^8.20.0",

29 "axios": "^1.20.0",

30 "commander": "^11.0.0",

31 "js-yaml": "^4.3.2"

32 },

33 "engines": {

34 "node": ">=18.0.0"

35 },

36 "keywords": [

37 "hone",

38 "ai",

39 "sdlc",

40 "pipeline",

41 "enterprise",

42 "developer-tools"

43 ],

44 "author": "Hone AI",

hone-cli.jsView file

Lines 5-45javascript

5 *

6 * Bridges the gap between setup-ai-pipeline.sh v3.1 and the Hone server.

7 * The key insight: setup-ai-pipeline.sh needs ENTERPRISE_SOURCE = enterprise-github

bin/hone-mcp.jsView file

Lines 1-11javascript

1#!/usr/bin/env node

2'use strict';

3// HC-COMM-012 (A1 P1): entry point for the Hone MCP server (stdio).

4// Registered by the Claude Code plugin's .mcp.json as `npx -y @hone-ai/cli hone-mcp`

5// (or `hone-mcp` once installed). Delegates to ../mcp-server.js `start()`.

6// detached-ok: top-level entrypoint - the process lifetime IS the await, and no caller exists to observe it

7require('../mcp-server.js').start().catch((e)

lib/hook-templates/pre-push.shView file

•path = lib/hook-templates/pre-push.sh kind = build_helper sizeBytes = 2812 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

lib/hook-templates/pre-push.shView on unpkg

lib/auto-verify.js#virtual:normalized:round1View file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 15

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

lib/auto-verify.js#virtual:normalized:round1View on unpkg

lib/performance-analyzer.jsView file

•matchType = normalized_sha256 matchedPackage = @hone-ai/cli@1.28.0 matchedPath = lib/performance-analyzer.js matchedIdentity = npm:QGhvbmUtYWkvY2xp:1.28.0 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

lib/performance-analyzer.jsView on unpkg

Lines 1283-1323javascript

1283 const installE2e = opts && opts.e2e !== false && opts.noE2e !== true;

1284 if (installE2e) {

1285 console.log('');

1286 console.log(` Skipping Playwright (Python) e2e auto-install — adopters opt in via \`pip install pytest-playwright\` separately.`);

1287 console.log(` See pytest-playwright docs for details.`);

1288 }

1289}

1290

1291async function installTestFramework(repoRoot, opts) {

1292 console.log('');

1293 console.log('── Test Framework Setup ────────────────────────────────');

1294 console.log('');

1295

1296 const detected = detectExistingTestFramework(repoRoot);

1297 const pkgs = getInstallPackages(detected.stack);

1298

1299 // H-002b: Python branch — different install commands + pyproject.toml (not package.json)

1300 if (pkgs.pkgManagerKind === 'python') {

1301 return installPythonTestFramework(repoRoot, detected, pkgs, opts);

1302 }

1303

1304 const installCmd = detected.pkgMgr === 'yarn' ? 'yarn add -D' : detected.pkgMgr === 'pnpm' ? 'pnpm add -D' : 'npm install -D';

1305

1306 // ── Unit test framework ────────────────────────────────

1307 if (detected.testFw) {

1308 console.log(` Test framework detected: ${detected.testFw} ✓ (skipping install)`);

1309 } else {

1310 console.log(` Stack: ${detected.stack} → Installing: ${pkgs.unit.join(', ')}`);

1311 try {

1312 execSync(`${installCmd} ${pkgs.unit.join(' ')}`, { stdio: 'inherit', cwd: repoRoot });

1313 console.log(` ✓ Unit test framework installed`);

High

Runtime Package Install

Package source invokes a package manager install command at runtime.

hone-cli.jsView on unpkg · L1303

1314 } catch (e) {

1315 console.error(` ✗ Install failed: ${e.message}`);

1316 return;

1317 }

1318 }

1319

1320 // ── Test config file ───────────────────────────────────

1321 if (detected.hasTestConfig) {

1322 console.log(` Test config exists ✓ (skipping creation)`);

1323 } else {

Lines 8040-8080javascript

8040 // fix; it does not quietly fall through to "tests passed", which would report a green

8041 // verdict for code whose stored-state behaviour was never exercised.

8042 try {

8043 const { readSandboxConfig, assertScratchTarget } = require('./lib/pipeline-config');

8044 const { planSandboxRun, parseProbeOutput, describeProbeResult, sandboxSuiteVerdict } = require('./lib/sandbox-lifecycle');

8045 const plan = planSandboxRun({

8046 sandbox: readSandboxConfig(process.cwd()),

8047 axes: runConfig?.classifier_axes || runConfig?.axes || [],

8048 capability: runConfig?.capability || null,

8049 });

8050 if (plan.refuse) {

8051 emit({ ok: false, verdict: 'sandbox_refused', detail: plan.reason },

8052 `✗ sandbox refused: ${plan.reason}`);

8053 exitCode = EXIT.FAIL;

8054 reportVerdict = 'sandbox_refused'; reportDetail = plan.reason;

8055 throw new Error('sandbox refused');

8056 }

8057 if (plan.engage) {

8058 // The probe runs in the REAL tree, not the worktree: it reads the adopter's live

8059 // datastore, which the worktree does not change.

8060 const probed = spawnSync(plan.probe, {

8061 cwd: process.cwd(), shell: true, encoding: 'utf8',

8062 timeout: 60_000, env: verifyCommandEnv(gitEnv()), stdio: ['ignore', 'pipe', 'pipe'],

High

Shell

Package source references shell execution.

hone-cli.jsView on unpkg · L8060

8063 });

8064 // A probe that exited non-zero is not evidence, whatever it left on stdout — a

8065 // command that fails partway can still print a stale or partial line, and reading it

8066 // would turn a failed check into a pass.

8067 if (probed.status !== 0) {

8068 throw new Error(`sandbox probe exited ${probed.status === null ? 'abnormally' : probed.status}`

8069 + ` (${plan.probe}): ${((probed.stderr || '').split('\n')[0] || 'no stderr')}`);

8070 }

8071 // The guard reads the LIVE connection and nothing else (HC-GF-169).

8072 const probeEvidence = parseProbeOutput(probed.stdout);

8073 assertScratchTarget(plan.verify, probeEvidence);

8074 // HC-GF-190: say what the guard PROVED. It throws on refusal and returns nothing on

8075 // success, so a passing guard was silent — and HC-GF-185's acceptance ("the output

8076 // shows the probe, the guard verdict and the teardown") stayed open on run 6be117b3,

8077 // where all three had in fact happened. Printed after the check and before the first

8078 // write, so it describes something that has already occurred.

8079 if (opts.format !== 'json') console.log(` sandbox: ${describeProbeResult(plan.verify, probeEvidence)}`);

8080 // Armed BEFORE the first command, not after the last. `create` succeeding and