@deftai/directive-content@0.111.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-aiThe package is content and hook support with no registry-install lifecycle hook or runtime self-dependency. The shipped hook resolver is user-configured Git-hook functionality, not an automatic install-time control-surface mutation.
Decision evidence
public snapshot- The package ships a Git-hook helper that can invoke a globally installed `deft` command when a hook is explicitly enabled.
- The manifest has pack-time scripts; its postpack command removes staged package contents after packing.
- There are no preinstall, install, or postinstall lifecycle hooks.
- The hook scripts run only as Git hooks after explicit configuration and contain no network or credential collection logic.
- No dependencies, self-dependencies, network endpoints, obfuscated payloads, or automatic consumer-project mutation were 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 unpkgThe package ships a Git-hook helper that can invoke a globally installed `deft` command when a hook is explicitly enabled.
.githooks/_deft-run.shView on unpkg · L31Findings
Affected versions and remediation
This report applies to @deftai/directive-content@0.111.0.
See all versions of @deftai/directive-content for other recorded verdicts.
- Review the evidence and your use of @deftai/directive-content@0.111.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.