registry / @deftai/directive-content / 0.112.0

@deftai/directive-content@0.112.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-ai

The package is a content deposit with no install-time lifecycle and no declared dependency chain. Its executable hook helper is readable and user-triggered, and the inspected code shows no concrete malicious behavior.

Static reason

No blocking static signals were detected.

Trigger

A user must explicitly configure and run the shipped Git hooks or create a package archive.

Impact

No credential theft, network exfiltration, persistence, or destructive behavior was found in the inspected execution paths.

Mechanism

User-invoked Git-hook CLI dispatch and publish-time staging.

AI rationale

Decision evidence

public snapshot

AI called this Clean at 94.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The package ships a readable Git hook resolver that can invoke a local or PATH-resolved CLI when a hook runs.
The manifest has packaging scripts, so its publish-time staging helper can spawn Node during pack creation.

Evidence against

No preinstall, install, or postinstall lifecycle hook is declared.
No dependencies or self-dependency are declared.
The inspected hook resolver contains no network, credential collection, or file-write operation.
Hook activation is behind the user-invoked setup task, not npm installation.

Behavioral surface

Source

ChildProcessEnvironmentVarsFilesystemShell

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 6 file(s), 41.4 KB of source

Source & flagged code

4 flagged

.githooks/_deft-run.shView file

Lines 11-48text

11# 3. Consumer install (vendored .deft/core, no local build): resolve the

12# global `deft` exactly as before -- consumers have no local CLI to prefer.

13# 4. Local build present without the monorepo sentinel: fall back to it.

14# 5. Nothing resolvable: fail with an install hint.

16run_deft() {

17 _deft_local="$REPO_ROOT/packages/cli/dist/bin.js"

19 # (1) Escape hatch: force the global even in a monorepo.

20 if [ "${DEFT_HOOKS_PREFER_GLOBAL:-}" = "1" ] && command -v deft >/dev/null 2>&1; then

21 deft "$@"

22 return $?

23 fi

25 # (2) Framework-source checkout: the local build is authoritative for verbs.

26 if [ -f "$_deft_local" ] && [ -f "$REPO_ROOT/pnpm-workspace.yaml" ]; then

27 node "$_deft_local" "$@"

28 return $?

29 fi

31 # (3) Consumer install: resolve the global `deft` exactly as today.

32 if command -v deft >/dev/null 2>&1; then

33 deft "$@"

34 return $?

35 fi

Low

Ai Review Evidence

The package ships a readable Git hook resolver that can invoke a local or PATH-resolved CLI when a hook runs.

.githooks/_deft-run.shView on unpkg · L31

37 # (4) Local build present without the monorepo sentinel.

38 if [ -f "$_deft_local" ]; then

39 node "$_deft_local" "$@"

40 return $?

41 fi

43 # (5) Nothing resolvable.

44 echo "deft hooks: 'deft' not found on PATH and no local CLI at packages/cli/dist/bin.js." >&2

45 echo " Install: npm i -g @deftai/directive" >&2

46 exit 1

47}

•path = .githooks/_deft-run.sh kind = payload_in_excluded_dir sizeBytes = 1873 magicHex = [redacted]

High

Payload In Excluded Dir

Package hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.

.githooks/_deft-run.shView on unpkg

•path = .githooks/_deft-run.sh kind = build_helper sizeBytes = 1873 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

.githooks/_deft-run.shView on unpkg

package.jsonView file

21"scripts": { "prepack": "node ./stage-pack.mjs", "postpack": "node --input-type=module -e \"import{readdirSync,rmSync}from'node:fs';import{dirname,join}from'node:path';import{fileURLToPath}from'node:url';const pkg=dirname(fileURLToPath(import.meta.url));const keep=new Set(['package.json','stage-pack.mjs']);for(const name of readdirSync(pkg)){if(keep.has(name))continue;rmSync(join(pkg,name),{recursive:true,force:true});}\"" }

Low

Ai Review Evidence

The manifest has packaging scripts, so its publish-time staging helper can spawn Node during pack creation.

package.jsonView on unpkg · L21

Source & flagged code

4 flagged · loading source

.githooks/_deft-run.shView file

•path = .githooks/_deft-run.sh kind = payload_in_excluded_dir sizeBytes = 1873 magicHex = [redacted]

High

Payload In Excluded Dir

Package hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.

.githooks/_deft-run.shView on unpkg

•path = .githooks/_deft-run.sh kind = build_helper sizeBytes = 1873 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

.githooks/_deft-run.shView on unpkg

31# (3) Consumer install: resolve the global `deft` exactly as today. if command -v deft >/dev/null 2>&1; then deft "$@" return $? fi

Low

Ai Review Evidence

The package ships a readable Git hook resolver that can invoke a local or PATH-resolved CLI when a hook runs.

.githooks/_deft-run.shView on unpkg · L31

Findings

1 High3 Medium5 Low

HighPayload In Excluded Dir.githooks/_deft-run.sh

MediumEnvironment Vars

MediumShips Build Helper.githooks/_deft-run.sh

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowAi Review Evidence.githooks/_deft-run.sh

LowAi Review Evidencepackage.json

Affected versions and remediation

This report applies to @deftai/directive-content@0.112.0.

See all versions of @deftai/directive-content for other recorded verdicts.

Review the evidence and your use of @deftai/directive-content@0.112.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: 2026-09-07 10:33:51.771Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.