@deftai/directive-content@0.66.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 3mo ago · by lpm-firewall-aiThe package has no npm install lifecycle execution and its shipped shell hooks are transparent, repository-local helpers activated only by explicit setup. The only network operation is a named, user-invoked task downloading a pinned public GitHub archive.
Decision evidence
public snapshot- Taskfile.yml has explicit user-run setup that sets repository-local core.hooksPath.
- tasks/deployments.yml has an explicit cloudgov:sync task using curl.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Package contains documentation, YAML task definitions, and three transparent POSIX Git-hook scripts; no JS/native executable payload.
- .githooks/_deft-run.sh only resolves a deft CLI and forwards hook arguments.
- No credential harvesting, exfiltration, dynamic evaluation, binary loading, or import-time execution found.
Source & flagged code
2 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.66.0.
See all versions of @deftai/directive-content for other recorded verdicts.
- Review the evidence and your use of @deftai/directive-content@0.66.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.