yusufkhon-guard
Express.js va Node.js uchun yengil, mustaqil (zero-dependency) xavfsizlik middleware: aktiv himoya (blue team firewall), auto IP-ban, security headers, rate-limiting, input sanitization va audit-skaner.
This report shows the evidence for yusufkhon-guard@1.2.0. 1 of 2 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package deliberately rewrites consumer source during postinstall and causes runtime monkey-patching through the injected import. That concrete install-time behavior warrants blocking even though no exfiltration endpoint is present.
Decision evidence
public snapshot- The manifest runs a postinstall script automatically during installation.
- The postinstall script locates a consumer project's JavaScript entry file and writes an import into it.
- The injected import activates code that replaces Express's exported factory and adds middleware to every newly created app.
- This mutates unrelated consumer source without an explicit user command; an environment opt-out does not establish consent.
- The lifecycle code shows no credential collection or network transmission.
- The injected code is package-aligned Express middleware rather than a remote payload.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references dynamic require/import behavior.
bin/ai.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to yusufkhon-guard@1.2.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing yusufkhon-guard@1.2.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.