registry / Destructive action / @deftai/directive-content / 0.119.2

@deftai/directive-content@0.119.2

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 14d ago · by lpm-firewall-ai

The postpack hook contains a concrete destructive action against the package directory, so this is malicious rather than a clean result. The trigger is packaging, not consumer installation.

Static reason

No blocking static signals were detected.

Trigger

A maintainer runs npm pack or another operation that invokes postpack.

Impact

This can erase the package’s source and other files from the maintainer’s checkout.

Mechanism

The hook recursively deletes each top-level entry under its package directory except package.json and stage-pack.mjs.

Attack narrative

The package defines no install-time lifecycle hook, but its postpack script performs recursive deletion across its own package directory. This is destructive when packaging runs and can remove the checkout’s package contents.

AI rationale

The postpack hook contains a concrete destructive action against the package directory, so this is malicious rather than a clean result. The trigger is packaging, not consumer installation.

Evidence

package.json

Decision evidence

public snapshot

AI called this Malicious at 96.0% confidence as Malware with low false-positive risk.

Evidence for block

The package’s postpack hook recursively removes every top-level entry in the package directory except package.json and stage-pack.mjs.
The required shell helper resolves and invokes the local or global deft CLI when called; it does not itself install or execute a payload.

Evidence against

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 1-40text

1# Shared deft CLI resolver for .githooks/* (#2067, #2248).

2# REPO_ROOT must be set before sourcing.

4# Resolution order:

5# 1. DEFT_HOOKS_PREFER_GLOBAL=1 forces the global `deft` (escape hatch, #2248).

6# 2. Framework-source (monorepo) checkout: prefer the freshly-built LOCAL CLI

7# (packages/cli/dist/bin.js) over a possibly-stale global `deft`, so a

8# newly-added-and-wired verb is not unknown to the global and does not

9# block commits/pushes (#2248). Detected via the built local CLI existing

10# under $REPO_ROOT together with a monorepo sentinel (pnpm-workspace.yaml).

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.

High

Ai Review Evidence

The required shell helper resolves and invokes the local or global deft CLI when called; it does not itself install or execute a payload.

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

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

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

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

39 node "$_deft_local" "$@"

40 return $?

•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

Lines 3-26json

3 "version": "0.119.2",

4 "deftConsumerDeposit": true,

5 "description": "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.",

6 "license": "MIT",

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

20if [ "${DEFT_HOOKS_PREFER_GLOBAL:-}" = "1" ] && command -v deft >/dev/null 2>&1; then deft "$@" return $? fi # (2) Framework-source checkout: the local

High

Ai Review Evidence

The required shell helper resolves and invokes the local or global deft CLI when called; it does not itself install or execute a payload.

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

•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

Findings

3 High3 Medium3 Low

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

HighAi Review Evidencepackage.json

HighAi Review Evidence.githooks/_deft-run.sh

MediumEnvironment Vars

MediumShips Build Helper.githooks/_deft-run.sh

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

Affected versions and remediation

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

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

Avoid installing @deftai/directive-content@0.119.2. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-10-08 15:48:57.691Z (UTC).

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

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Related packages

Other destructive action packages

Behavioral surface

Related packages

Other destructive action packages

Source & flagged code