lintai docs

Appearance

Rule Reference

SEC744lintai-ai-securitysupply-chainhardeningstablejsonwarn

package.json: git or forge dependency source

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

Public lane
supply-chain
Category
hardening
Provider
lintai-ai-security
Scope
per-file
Surface
json
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message only
How to read this lane

Reproducibility, provenance, and dependency hardening review.

How to read this category

Least-privilege, provenance, or operational hygiene signal.

Activation Model

Preset Activation

These presets explain where this rule appears in the product experience.

supply-chainsidecar lane

Lifecycle

Stable Lifecycle Contract

State

stable

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 positioned as a supply-chain hardening control: high-precision and actionable, but not a blanket claim of direct repository compromise.

Nearby Signals

Related Rules

SEC302Config: insecure HTTP endpointConfiguration contains an insecure http:// endpointsupply-chainhardeningjson
SEC304Config: TLS verification disabledConfiguration disables TLS or certificate verificationsupply-chainhardeningjson
SEC330MCP config: remote content piped to shellMCP configuration command downloads remote content and pipes it into a shellsupply-chainsecurityjson
SEC331MCP config: TLS verification disabledMCP configuration command disables TLS verification in a network-capable execution pathsupply-chainhardeningjson
SEC337MCP config: Docker image not digest-pinnedMCP configuration launches Docker with an image reference that is not digest-pinnedsupply-chainhardeningjson
SEC343Plugin hook: mutable package launcherPlugin hook command uses a mutable package launchersupply-chainhardeningjson

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.