@rowansenne/docnexus@0.23.0
[English README](./README.md)
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected agent configuration changes are reached through explicit CLI setup with selected targets. These changes implement the package's project-level agent integration; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json declares a CLI entry and ordinary build, prepack, and test scripts; it declares no install lifecycle hook.
- Agent instruction files are selected by the explicit Claude or Codex target.
- Skill links go under the selected project's .claude/skills or .agents/skills directory.
- The init command passes selected --agent targets into project initialization, which links skills for those targets.
- Linking installs a marked DocNexus block in the project instruction file; it reads the existing file and writes the resulting content.
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 links go under the selected project's .claude/skills or .agents/skills directory.
dist/src/skills.jsView on unpkg · L30Findings
Affected versions and remediation
This report applies to @rowansenne/docnexus@0.23.0.
See all versions of @rowansenne/docnexus for other recorded verdicts.
- Review the evidence and your use of @rowansenne/docnexus@0.23.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.