@deftai/directive-content@0.101.0
Shippable Directive framework content in the consumer .deft/core/ layout (C1 flatten), plus the engine surfaces (.githooks/, Taskfile.yml, tasks/) the deposit wires. Python-free per #2022 Phase 3. Refs #11, #1669, #1967.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection found a content/tooling package with no npm install lifecycle hooks. Its hook and network-related actions are explicit user-invoked development tasks, with no concrete malicious chain.
Decision evidence
public snapshot- Explicit `task setup` can set the repository-local Git hooks path.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Hook execution is activated only through explicit setup and runs named Deft verification commands.
- Child-process helpers use non-shell spawning and validate command inputs.
- The sole network fetch is an explicitly named cloudgov sync task, not install/import behavior.
Source & flagged code
3 flagged · loading sourcePackage hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.
.githooks/_deft-run.shView on unpkgPackage ships non-JavaScript build or shell helper files.
.githooks/_deft-run.shView on unpkgFindings
Affected versions and remediation
This report applies to @deftai/directive-content@0.101.0.
See all versions of @deftai/directive-content for other recorded verdicts.
- Review the evidence and your use of @deftai/directive-content@0.101.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.