lintai docs

Appearance

Rule Reference

SEC744lintai-ai-securitystablejsonwarn

package.json: git or forge dependency source

package.json installs a dependency from a git or forge shortcut source

Provider
lintai-ai-security
Surface
json
Scope
per_file
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

supply-chainmembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks committed package.json dependency sections for direct git or forge shortcut sources that bypass the normal registry release path.

Deterministic signal basis

JsonSignals package manifest analysis over dependency sections for specs starting with `git://`, `git+https://`, `git+ssh://`, `github:`, `gitlab:`, or `bitbucket:`.

Malicious corpus
package-manifest-git-url-dependency
Benign corpus
package-manifest-registry-dependency-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

SEC743package.json: dangerous lifecycle scriptpackage.json defines a dangerous install-time lifecycle scriptjsonstable
SEC745package.json: unbounded dependency versionpackage.json uses an unbounded dependency version like * or latestjsonstable
SEC753package.json: direct archive URL dependency sourcepackage.json installs a dependency from a direct archive URL sourcejsonstable
SEC301MCP config: shell trampolineMCP configuration shells out through sh -c or bash -cjsonstable
SEC302Config: insecure HTTP endpointConfiguration contains an insecure http:// endpointjsonstable
SEC303MCP config: credential env passthroughMCP configuration passes through credential environment variablesjsonstable

Why It Matters ​

Direct git and forge shortcut dependencies bypass the normal registry release path, which makes provenance, review, and repeatability weaker than consuming a published package release.

What Triggers ​

SEC744 matches dependency entries in package.json that point to direct source locations such as git://, git+https://, git+ssh://, github:, gitlab:, or bitbucket:.

False Positives ​

Some teams intentionally pin internal dependencies to source URLs, but this still expands supply-chain risk and deserves explicit review rather than silent acceptance in a shared manifest.

Remediation ​

Prefer a published registry release when possible, or document and tightly review any direct source dependency that must remain.