gitlens@0.0.1-security
security holding package
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection found only metadata and README content, with no executable entrypoints or lifecycle hooks. The package is a security holding placeholder rather than an active payload carrier.
Static reason
No blocking static signals were detected.
Trigger
None identified
Impact
No malicious behavior observed in inspected source
Mechanism
metadata-only security holding package
AI rationale
Static inspection found only metadata and README content, with no executable entrypoints or lifecycle hooks. The package is a security holding placeholder rather than an active payload carrier.
Evidence
package.jsonREADME.md
Decision evidence
public snapshotAI called this Clean at 98.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
Evidence against
- package.json contains only name, version, description, and repository; no scripts, entrypoints, bin, dependencies, or files fields.
- README.md identifies this as an npm security holding package placeholder.
- Package file listing contains only package.json and README.md.
- Search found no child_process, eval, network, credential access, lifecycle hooks, or agent control-surface writes.
Behavioral surface
NoLicense
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 Low
LowNo License
Affected versions and remediation
This report applies to gitlens@0.0.1-security.
See all versions of gitlens for other recorded verdicts.
- Review the evidence and your use of gitlens@0.0.1-security 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.