Dependency Security Check
When to use
- Adding a new dependency to any project
- Running pip install, npm install, go get, or equivalent
- Auditing existing dependencies for supply-chain risk
- Reviewing a PR that adds or updates dependencies
- Investigating a potential supply-chain compromise
Skip when
- No dependencies are being added, updated, or audited
- Task involves only internal code changes with no new imports
- Dependency is already vetted and pinned in lockfile
Related
Complementary: ring:hardening-dockerfiles, ring:implementing-tasks
Supply-chain gate for every install command in a Lerian codebase.
Pre-Install Checks
1. Package Identity Verification
For every package, verify:
├── Typosquatting: compare against known popular packages
│ e.g., "requets" vs "requests", "rnodule" vs "module"
├── Homoglyph attacks: look-alike Unicode characters
├── Maintainer risk:
│ - Single maintainer = higher risk
│ - Account age < 6 months = flag
│ - Recent ownership transfer = CRITICAL flag
└── Package age: < 30 days = flag
2. Vulnerability Database Check
| Source |
Ecosystem |
What It Covers |
| OSV.dev |
All |
Google aggregated CVEs |
| GitHub Advisory Database |
All |
GHSA linked to CVEs |
| Socket.dev |
npm, pip |
Supply-chain: install scripts, network access |
| PyPI JSON API |
pip |
Metadata, maintainers, release history |
| npm registry API |
npm |
Metadata, maintainers, install scripts |
| Go vulnerability DB (vuln.go.dev) |
Go |
Official Go CVE database |
3. Behavioral Signals
| Signal |
Risk Level |
Description |
| Install scripts |
HIGH |
postinstall (npm), setup.py subprocess |
| Network access at import |
CRITICAL |
Package phones home on import |
| File system access outside project |
HIGH |
Reads ~/.ssh, ~/.aws, env vars |
| Obfuscated code |
CRITICAL |
Base64 payloads, eval(), exec() |
| Native binary bundled |
HIGH |
Pre-compiled binaries without source |
4. Lockfile Integrity
| Ecosystem |
Lockfile |
Hash Requirement |
| Go |
go.sum |
SHA-256 native — Go handles automatically |
| npm |
package-lock.json |
integrity field (SHA-512) must be present for ALL deps |
| pip |
requirements.txt |
--require-hashes MUST be enforced |
| Cargo |
Cargo.lock |
checksum field verification |
Risk Scoring
risk_score = weighted_sum(
typosquatting_similarity * 25,
maintainer_risk * 20,
package_age_risk * 15,
vulnerability_count * 20, # weighted by severity
behavioral_flags * 15,
lockfile_integrity * 5
)
Score thresholds:
- 0-25: LOW — proceed
- 26-50: MEDIUM — proceed with documentation
- 51-75: HIGH — escalate to Fred before installing
- 76-100: CRITICAL — block installation
Decision Matrix
| Risk Level |
Action |
| LOW (0-25) |
✅ Approve — document in PR |
| MEDIUM (26-50) |
⚠️ Conditional — mitigations required |
| HIGH (51-75) |
🚨 Escalate to Fred before installing |
| CRITICAL (76-100) |
❌ Block — do not install |
Report Template
## Dependency Security Report
Package: {name} @ {version}
Ecosystem: {go|npm|pip}
Risk Score: {score}/100 — {LOW|MEDIUM|HIGH|CRITICAL}
### Verification Results
| Check | Status | Details |
|-------|--------|---------|
| Typosquatting check | PASS/FLAG | {comparison} |
| Maintainer verification | PASS/FLAG | {maintainer count, age} |
| Vulnerability scan | PASS/FLAG | {CVE count, severity} |
| Behavioral analysis | PASS/FLAG | {signals found} |
| Lockfile integrity | PASS/FAIL | {hash present/missing} |
### Decision
{APPROVED|CONDITIONAL|ESCALATE|BLOCKED}
### Required Actions (if not APPROVED)
1. {specific mitigations or alternatives}
Mitigations for MEDIUM Risk
- Pin exact version in lockfile
- Vendor the dependency (copy source into repo)
- Document why this specific package was chosen over alternatives
- Add to security monitoring (e.g., GitHub Dependabot alerts)
1---2name: ring-auditing-dependency-security3description: Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a dependency PR, or investigating a compromise. Skip when no new dependency is involved or it is already vetted.4---56# Dependency Security Check78## When to use9- Adding a new dependency to any project10- Running pip install, npm install, go get, or equivalent11- Auditing existing dependencies for supply-chain risk12- Reviewing a PR that adds or updates dependencies13- Investigating a potential supply-chain compromise1415## Skip when16- No dependencies are being added, updated, or audited17- Task involves only internal code changes with no new imports18- Dependency is already vetted and pinned in lockfile1920## Related21**Complementary:** ring:hardening-dockerfiles, ring:implementing-tasks222324Supply-chain gate for every install command in a Lerian codebase.2526## Pre-Install Checks2728### 1. Package Identity Verification2930```31For every package, verify:32├── Typosquatting: compare against known popular packages33│ e.g., "requets" vs "requests", "rnodule" vs "module"34├── Homoglyph attacks: look-alike Unicode characters35├── Maintainer risk:36│ - Single maintainer = higher risk37│ - Account age < 6 months = flag38│ - Recent ownership transfer = CRITICAL flag39└── Package age: < 30 days = flag40```4142### 2. Vulnerability Database Check4344| Source | Ecosystem | What It Covers |45|--------|-----------|----------------|46| OSV.dev | All | Google aggregated CVEs |47| GitHub Advisory Database | All | GHSA linked to CVEs |48| Socket.dev | npm, pip | Supply-chain: install scripts, network access |49| PyPI JSON API | pip | Metadata, maintainers, release history |50| npm registry API | npm | Metadata, maintainers, install scripts |51| Go vulnerability DB (vuln.go.dev) | Go | Official Go CVE database |5253### 3. Behavioral Signals5455| Signal | Risk Level | Description |56|--------|-----------|-------------|57| Install scripts | HIGH | `postinstall` (npm), `setup.py` subprocess |58| Network access at import | CRITICAL | Package phones home on import |59| File system access outside project | HIGH | Reads `~/.ssh`, `~/.aws`, env vars |60| Obfuscated code | CRITICAL | Base64 payloads, eval(), exec() |61| Native binary bundled | HIGH | Pre-compiled binaries without source |6263### 4. Lockfile Integrity6465| Ecosystem | Lockfile | Hash Requirement |66|-----------|----------|-----------------|67| Go | go.sum | SHA-256 native — Go handles automatically |68| npm | package-lock.json | `integrity` field (SHA-512) must be present for ALL deps |69| pip | requirements.txt | `--require-hashes` MUST be enforced |70| Cargo | Cargo.lock | `checksum` field verification |7172## Risk Scoring7374```75risk_score = weighted_sum(76 typosquatting_similarity * 25,77 maintainer_risk * 20,78 package_age_risk * 15,79 vulnerability_count * 20, # weighted by severity80 behavioral_flags * 15,81 lockfile_integrity * 582)83```8485Score thresholds:86- 0-25: LOW — proceed87- 26-50: MEDIUM — proceed with documentation88- 51-75: HIGH — escalate to Fred before installing89- 76-100: CRITICAL — block installation9091## Decision Matrix9293| Risk Level | Action |94|-----------|--------|95| LOW (0-25) | ✅ Approve — document in PR |96| MEDIUM (26-50) | ⚠️ Conditional — mitigations required |97| HIGH (51-75) | 🚨 Escalate to Fred before installing |98| CRITICAL (76-100) | ❌ Block — do not install |99100## Report Template101102```markdown103## Dependency Security Report104105Package: {name} @ {version}106Ecosystem: {go|npm|pip}107Risk Score: {score}/100 — {LOW|MEDIUM|HIGH|CRITICAL}108109### Verification Results110111| Check | Status | Details |112|-------|--------|---------|113| Typosquatting check | PASS/FLAG | {comparison} |114| Maintainer verification | PASS/FLAG | {maintainer count, age} |115| Vulnerability scan | PASS/FLAG | {CVE count, severity} |116| Behavioral analysis | PASS/FLAG | {signals found} |117| Lockfile integrity | PASS/FAIL | {hash present/missing} |118119### Decision120{APPROVED|CONDITIONAL|ESCALATE|BLOCKED}121122### Required Actions (if not APPROVED)1231. {specific mitigations or alternatives}124```125126## Mitigations for MEDIUM Risk127128- Pin exact version in lockfile129- Vendor the dependency (copy source into repo)130- Document why this specific package was chosen over alternatives131- Add to security monitoring (e.g., GitHub Dependabot alerts)
LerianStudio