SLOPGUARD enforces deterministic Policy-as-Code before AI-generated packages enter your build process.
Definite 404 on official registry. Hallucination intercepted.
Damerau-Levenshtein distance 1 to popular package 'requests'.
| Import Specifier | Canonical Package | Registry Status | Gate Verdict | Risk Level | Reason & Evidence | Action |
|---|---|---|---|---|---|---|
| No scan executed yet. Click "Execute SLOPGUARD Scan" above. | ||||||
| Package Name | Ecosystem | Identity Status | Registry Status | Gate Verdict | Risk | Details |
|---|
Traceable relationship flow: IMPORT ➔ PACKAGE ➔ RELEASE ➔ REPOSITORY ➔ PROVENANCE ➔ ADVISORY. Click nodes for raw evidence.
Tracks dependencies that failed verification when observed in AI code. If a phantom package suddenly appears on a registry (NOT_FOUND ➔ APPEARED), an immediate ALERT is triggered to neutralize dependency hallucination pre-registration exploits.
| Package Name | Ecosystem | Current State | Observation Count | First Seen | State Transitions |
|---|
Proposes verified replacements for unresolved, typosquatted, or deprecated libraries. Patches must pass the full control plane rescan before acceptance.
Intercepts autonomous agent installation commands (e.g. pip install <package>) before execution. Evaluates policy in real time.
Test policy rules against real evidence without executing any install actions.
Query: "Why did SLOPGUARD block or quarantine this package?" Reconstructs the exact immutable evidence trail.
| Timestamp | Event Type | Actor | Package | Action | Details |
|---|
Empirical evaluation results executed against live PyPI, npm, and OSV endpoints:
| Corpus Category | Tested Samples | Accuracy / Containment | Status |
|---|---|---|---|
| REAL (requests, numpy, express, lodash) | 4 | 100.0% | VERIFIED |
| PHANTOM (AI Hallucinated package names) | 3 | 100.0% | BLOCKED |
| TRICKY (cv2, PIL, yaml, stdlib) | 4 | 100.0% | RESOLVED |
| ADVERSARIAL (requets, numpу homoglyphs) | 2 | 100.0% | CONTAINED |