@rowansenne/docnexus@0.15.0
[English README](./README.md)
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe agent-integration writes are tied to explicit setup commands and are scoped to DocNexus skills and a marked project instruction block. The manifest has no install lifecycle hook, and ordinary CLI skill refreshes write within the DocNexus workspace.
Decision evidence
public snapshot- package.json exposes a CLI and has a prepack build script; it declares no install lifecycle hook or runtime self-dependency.
- Agent instruction files are updated by an explicit setup function, which inserts or refreshes a marked DocNexus block.
- Skill linking creates links in the selected agent project directory and then installs the corresponding instruction block.
- The CLI links skills only for an explicit skills link command or when init receives agent targets; init defaults to no targets.
- Ordinary CLI commands may refresh skills in the DocNexus workspace, while the agent-link command is handled separately.
Source & flagged code
6 flagged · loading sourceManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
dist/src/skills.jsView on unpkgSkill linking creates links in the selected agent project directory and then installs the corresponding instruction block.
dist/src/skills.jsView on unpkg · L24Findings
Affected versions and remediation
This report applies to @rowansenne/docnexus@0.15.0.
See all versions of @rowansenne/docnexus for other recorded verdicts.
- Review the evidence and your use of @rowansenne/docnexus@0.15.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.