Skip to main content

Threat feed How it works Policy

Threat feed How it works Policy

Loading npm security reports…

pi-usereq@0.51.0: Suspicious npm security report (Warn) | LPM Firewall

Skip to main content

Threat feed How it works Policy

Threat feed How it works Policy

Flagged — allowed with a warning

Allowed by default policy, but 13 finding(s) warrant review before installing.

View on npm All versions

registry / pi-usereq / 0.51.0

pi-usereq@0.51.0

<p align="center"> <img src="https://img.shields.io/badge/python-3.11%2B-3776AB?style=flat-square&logo=python&logoColor=white" alt="Python 3.11+"> <img src="https://img.shields.io/badge/license-GPL--3.0-491?style=flat-square" alt="License: GPL-3.0">

AI Security Review

scanned 6h ago · by lpm-firewall-ai

An automatic postinstall can change the consumer project's npm script approval policy. It approves every detected dependency with an install lifecycle script, which may permit those scripts to run.

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

npm runs this package's postinstall lifecycle script.

Impact

The consumer project can acquire lifecycle script approvals without an explicit approval step in this package's code, increasing the ability of dependencies to execute install scripts.

Mechanism

The script scans consumer node_modules and writes selected package names into the consumer package.json allowScripts map.

AI rationale

The postinstall performs an automatic write to the consumer project's package.json, approving detected dependency lifecycle scripts. This is a real install-time policy change, but the inspected source does not establish an attack chain that meets the block criteria.

Evidence

package.jsonscripts/install-static-checkers.ts

Decision evidence

public snapshot

AI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

package.json runs a postinstall script that invokes the checker installer.

Stop threats before they install.

Firewall

Threat feed
How it works
Policy

LPM

During postinstall, the installer scans the consumer project's node_modules and selects packages with install lifecycle scripts.

It adds the selected package names to the consumer project's allowScripts map and writes the updated package.json.

This automatically changes the consumer's script approval policy; source does not show a user confirmation step.

The notification code sends its configured payload to the fixed Pushover API endpoint.

Evidence against

The postinstall also checks for static checker tools and attempts to install missing ones under the package installation root.
The inspected notification request targets api.pushover.net, consistent with its Pushover integration.

Behavioral surface

Source

ChildProcessDynamicRequireEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

Manifest

NoLicense

scanned 37 file(s), 1.02 MB of source, external domains: api.pushover.net

Source & flagged code

5 flagged · loading source

package.jsonView file

•scripts.postinstall = node --import tsx ./scripts/install-static-checkers.ts

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•scripts.postinstall = node --import tsx ./scripts/install-static-checkers.ts

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg

scripts/lib/extension-debug-harness.tsView file

137const moduleUrl = pathToFileURL(extensionPath).href; L138: const loadedModule = await import(moduleUrl); L139: if (typeof loadedModule.default !== "function") {

Medium

Dynamic Require

Package source references dynamic require/import behavior.

scripts/lib/extension-debug-harness.tsView on unpkg · L137

scripts/pi-usereq-debug.shView file

•path = scripts/pi-usereq-debug.sh kind = build_helper sizeBytes = 14588 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

scripts/pi-usereq-debug.shView on unpkg

src/core/pi-notify.tsView file

•matchType = previous_version_dangerous_delta matchedPackage = pi-usereq@0.50.0 matchedIdentity = npm:cGktdXNlcmVx:0.50.0 similarity = 0.838 summary = stored previous version shares package body but lacks this dangerous source file

High

Previous Version Dangerous Delta

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

src/core/pi-notify.tsView on unpkg

Findings

2 High6 Medium5 Low

HighInstall Time Lifecycle Scriptspackage.json

HighPrevious Version Dangerous Deltasrc/core/pi-notify.ts

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumDynamic Requirescripts/lib/extension-debug-harness.ts

MediumNetwork

MediumEnvironment Vars

MediumShips Build Helperscripts/pi-usereq-debug.sh

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

LowNo License

Affected versions and remediation

This report applies to pi-usereq@0.51.0.

See version security history for other recorded verdicts.

Review the evidence and your use of pi-usereq@0.51.0 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-09 09:34:44.537Z (UTC).

91%Suspicious

AI assessment confidence

IntentDangerous Capability

TypeInstall Hook Abuse

False-positive riskMedium

Review stagesource_first_review

Firewall policyMatched warn-list

Package metadata

npm

Maintainersogekuri

Version0.51.0

Latest on npm0.76.0

PublishedSep 18, 2026

Licensenone

Dependencies10

Integrityverified

Package size576 KB

Files69

LinksRepository Homepage Issues

Runtime surface

package.json

EntrypointsNo public entrypoints declared.

RuntimeNo engine / OS / CPU constraints

Artifact1.98 MB · 69 files2 signature(s) · provenance

Install lifecyclepostinstall

Behavioral surface

ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkHighEntropyStringsUrlStringsNoLicense

LPM.dev Registry

© 2026 LPM

Source & flagged code

5 flagged

package.jsonView file

Lines 7-47json

7 },

8 "bugs": {

9 "url": "https://github.com/Ogekuri/PI-useReq/issues"

10 },

11 "homepage": "https://github.com/Ogekuri/PI-useReq#readme",

12 "type": "module",

13 "files": [

14 "src",

15 "scripts"

16 ],

17 "scripts": {

18 "test": "node --import tsx --test tests/**/*.test.ts",

19 "test:watch": "node --import tsx --test --watch tests/**/*.test.ts",

20 "cli": "node --import tsx ./src/cli.ts",

21 "debug:ext": "node --import tsx ./scripts/debug-extension.ts",

22 "debug:ext:inspect": "node --import tsx ./scripts/debug-extension.ts inspect",

23 "debug:ext:session": "node --import tsx ./scripts/debug-extension.ts session-start",

24 "debug:ext:command": "node --import tsx ./scripts/debug-extension.ts command",

25 "debug:ext:tool": "node --import tsx ./scripts/debug-extension.ts tool",

26 "debug:ext:sdk": "node --import tsx ./scripts/debug-extension.ts sdk-smoke",

27 "postinstall": "node --import tsx ./scripts/install-static-checkers.ts"

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L27

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg · L27

28 },

29 "pi": {

30 "extensions": [

31 "./src/index.ts"

32 ]

33 },

34 "peerDependencies": {

35 "@mariozechner/pi-ai": "*",

36 "@mariozechner/pi-coding-agent": "*",

37 "@mariozechner/pi-tui": "*",

38 "@sinclair/typebox": "^0.34.49"

39 },

40 "dependencies": {

41 "eslint": "^10.7.0",

42 "fast-glob": "^3.3.3",

43 "js-tiktoken": "^1.0.21",

44 "pyright": "^1.1.411",

45 "ruff": "^1.5.4",

46 "tsx": "^4.21.0"

47 },

scripts/lib/extension-debug-harness.tsView file

Lines 117-157typescript

117 const resolvedCwd = path.resolve(cwd ?? process.cwd());

118 if (!fs.existsSync(resolvedCwd) || !fs.statSync(resolvedCwd).

scripts/pi-usereq-debug.shView file

•path = scripts/pi-usereq-debug.sh kind = build_helper sizeBytes = 14588 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

scripts/pi-usereq-debug.shView on unpkg

src/core/pi-notify.tsView file

•matchType = previous_version_dangerous_delta matchedPackage = pi-usereq@0.50.0 matchedIdentity = npm:cGktdXNlcmVx:0.50.0 similarity = 0.838 summary = stored previous version shares package body but lacks this dangerous source file

High

Previous Version Dangerous Delta

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

src/core/pi-notify.tsView on unpkg

isDirectory

()) {

119 throw new ReqError(`Error: working directory not found: ${resolvedCwd}`, 1);

120 }

121 const resolvedExtensionPath = path.resolve(extensionPath ?? path.join(process.cwd(), "src", "index.ts"));

122 if (!fs.existsSync(resolvedExtensionPath) || !fs.statSync(resolvedExtensionPath).isFile()) {

123 throw new ReqError(`Error: extension entry not found: ${resolvedExtensionPath}`, 1);

124 }

125 return { cwd: resolvedCwd, extensionPath: resolvedExtensionPath };

126}

127

128/**

129 * @brief Loads the extension default export as a black-box factory.

130 * @details Performs a dynamic ESM import from the resolved extension path, verifies that the module exposes a callable default export, and returns that function without inspecting extension internals. Runtime is dominated by module loading. Side effects are limited to module evaluation.

131 * @param[in] extensionPath {string} Absolute extension entry path.

132 * @return {Promise<ExtensionFactory>} Loaded extension factory.

133 * @throws {ReqError} Throws when the module lacks a callable default export.

134 * @satisfies REQ-048

135 */

136export async function loadExtensionFactory(extensionPath: string): Promise<ExtensionFactory> {

137 const moduleUrl = pathToFileURL(extensionPath).href;

138 const loadedModule = await import(moduleUrl);

139 if (typeof loadedModule.default !== "function") {

Medium

Dynamic Require

Package source references dynamic require/import behavior.

scripts/lib/extension-debug-harness.tsView on unpkg · L137

140 throw new ReqError(`Error: extension default export is not callable: ${extensionPath}`, 1);

141 }

142 return loadedModule.default as ExtensionFactory;

143}

144

145/**

146 * @brief Executes a callback with `process.cwd()` temporarily set to the requested directory.

147 * @details Changes the current working directory before invoking the callback, records the effective cwd observed inside the callback, and restores the previous cwd in a `finally` block. Runtime is dominated by the callback. Side effects transiently mutate process cwd.

148 * @param[in] cwd {string} Requested working directory.

149 * @param[in] action {() => Promise<T> | T} Callback executed under the requested cwd.

150 * @return {Promise<{ value: T; effectiveProcessCwd: string }>} Callback result plus the cwd observed during execution.

151 */

152async function withProcessCwd<T>(cwd: string, action: () => Promise<T> | T): Promise<{ value: T; effectiveProcessCwd: string }> {

153 const previousCwd = process.cwd();

154 process.chdir(cwd);

155 try {

156 const value = await action();

157 return { value, effectiveProcessCwd: process.cwd() };