@deftai/directive-content@0.103.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-aiStatic source inspection found explicit-user development tooling, not an npm lifecycle payload or covert malicious chain. Network and project-control actions are confined to named Task commands rather than package installation or import.
Decision evidence
public snapshot- Ships user-invoked Git hooks and Task targets that can configure project tooling.
- package.json has no npm preinstall, install, or postinstall hook.
- Only executable package files are hook/Task helpers; no import-time entrypoint is declared.
- Hooks run only after explicit git hooksPath configuration and invoke the deft CLI.
- Task helpers use non-shell child-process dispatch and validate package-manager input.
- No credential harvesting, exfiltration, remote payload loading, or destructive install behavior found.
Source & flagged code
4 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 unpkgShips user-invoked Git hooks and Task targets that can configure project tooling.
Findings
Affected versions and remediation
This report applies to @deftai/directive-content@0.103.0.
See all versions of @deftai/directive-content for other recorded verdicts.
- Review the evidence and your use of @deftai/directive-content@0.103.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.