@rowansenne/docnexus@0.20.0
[English README](./README.md)
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe agent configuration writes are scoped to the project and are reached through explicit setup options, while routine skill refreshes stay in the DocNexus workspace. The inspected artifact is packaged data, and no malicious behavior was established.
Decision evidence
public snapshot- package.json exposes a CLI and declares no install lifecycle hook.
- Agent setup is initiated through an explicit skills-link command or an init option; init defaults to no agent targets.
- The integration adds a marked project-memory block that points agents to DocNexus recall and says to offer knowledge capture without storing it without user consent.
- Automatic skill refresh copies package skills into the project’s docnexus workspace; agent skill links target project-level agent directories.
- The required offline analysis identifies the flagged artifact as compressed UTF-8 data and reports no analysis limitations.
Source & flagged code
5 flagged · loading sourceManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
dist/src/skills.jsView on unpkgFindings
Affected versions and remediation
This report applies to @rowansenne/docnexus@0.20.0.
See all versions of @rowansenne/docnexus for other recorded verdicts.
- Review the evidence and your use of @rowansenne/docnexus@0.20.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.