registry / @devflow-tools/knowledge-engine / 0.18.0
@devflow-tools/knowledge-engine@0.18.0
Version-aware project knowledge ingestion and retrieval for DevFlow.
AI Security Review
scanned 26d ago · by lpm-firewall-aiInspected source explains the lifecycle hook and flagged Git helper as ordinary Playwright setup and documentation retrieval. No concrete attack behavior was found, so the scanner signals do not support a warning or block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The postinstall hook runs when the package is installed; documentation retrieval occurs when the engine synchronizes sources.
Impact
The inspected behavior installs a browser dependency and imports public documentation into the knowledge store; no harmful effect was established.
Mechanism
The hook invokes Playwright's Chromium installer. Sync code fetches configured HTML sources and documentation from Context7 or GitHub.
AI rationale
Inspected source explains the lifecycle hook and flagged Git helper as ordinary Playwright setup and documentation retrieval. No concrete attack behavior was found, so the scanner signals do not support a warning or block.
Evidence
package.jsondist/git-fetcher.jsdist/knowledge-engine.jsdist/context7-fetcher.js
Network endpoints2
context7.com/api/v2/contextgithub.com/${repo}.git
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall command installs Chromium through Playwright, a conventional browser setup step.
- Git documentation retrieval is implemented as an explicit repository and path based fetcher.
- The engine calls the GitHub and Context7 fetchers for built-in sources during document sync.
- HTML retrieval uses URLs in the source manifest and stores fetched content as documentation.
Evidence against
- No inspected source showed credential harvesting, unrelated endpoint forwarding, stealth persistence, destructive behavior, or hidden payload execution.
- The flagged Git helper clones a caller-selected GitHub repository and reads Markdown files; its command arguments are passed separately to git.
- Network requests are directed to Context7, GitHub documentation repositories, or manifest-provided documentation URLs.
Behavioral surface
ChildProcessCryptoFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedpackage.jsonView file
•scripts.postinstall = playwright install chromium || true
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = playwright install chromium || true
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg18"postinstall": "playwright install chromium || true"
},
"dependencies": {
"@devflow-tools/provider-runtime": "0.18.0",
"@devflow-tools/sdk": "0.
Low
Suspicious Lifecycle Evidence
The postinstall command installs Chromium through Playwright, a conventional browser setup step.
package.jsonView on unpkg · L18dist/git-fetcher.js
Findings
2 High3 Medium7 Low
HighInstall Time Lifecycle Scriptspackage.json
HighPrevious Version Dangerous Deltadist/git-fetcher.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/git-fetcher.js
LowAi Review Evidencedist/knowledge-engine.js
Affected versions and remediation
This report applies to @devflow-tools/knowledge-engine@0.18.0.
See all versions of @devflow-tools/knowledge-engine for other recorded verdicts.
- Review the evidence and your use of @devflow-tools/knowledge-engine@0.18.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.