@levo-so/next-middleware
Next middleware to add a proxy for levo integration in apps
This report shows the evidence for @levo-so/next-middleware@0.3.32. 1 of 24 known versions is blocked or flagged. The newest version, 0.3.34, is allowed. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe “REVIEW-SKIP” source comment attempts to suppress review of a stated duplicate-source gap, which the rules classify as malicious reviewer manipulation. The inspected executable code otherwise matches the package’s stated middleware purpose.
Decision evidence
public snapshot- dist/geoIp.js contains a “REVIEW-SKIP” comment stating there is no parity check between duplicate source copies and claiming the packaged code is byte-identical to the other copy.
- The executable entry point is a Next.js middleware proxy for Levo API and SEO file requests.
- No install scripts or automatic file writes were found; the GeoIP and parameter modules transform caller-supplied headers and route parameters.
Source & flagged code
1 flaggeddist/geoIp.js contains a “REVIEW-SKIP” comment stating there is no parity check between duplicate source copies and claiming the packaged code is byte-identical to the other copy.
dist/geoIp.jsView on unpkg · L15Findings
Affected versions and remediation
This report applies to @levo-so/next-middleware@0.3.32.
The versions list below shows the verdict for each recorded version.
- Avoid installing @levo-so/next-middleware@0.3.32. 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.