@levo-so/next-middleware@0.3.34
Next middleware to add a proxy for levo integration in apps
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected source matches the package's stated Next.js proxy purpose: matching requests are rewritten to Levo API hosts, while the helper exports parse supplied data. No install hooks or unrelated network behavior were found.
Decision evidence
public snapshot- The package entry point is dist/index.js, and the manifest declares sideEffects false.
- The middleware defaults to the documented Levo API hosts and rewrites matching Levo API paths to those services.
- The GeoIP export extracts country and language data from supplied headers; it does not make network requests.
- The declared npm scripts are build, type checking, cleanup, and development watch commands.
Source & flagged code
6 flaggedSource fingerprint signature matches a known malicious package signature; route for source-aware review.
dist/index.jsView on unpkgThe middleware defaults to the documented Levo API hosts and rewrites matching Levo API paths to those services.
dist/index.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to @levo-so/next-middleware@0.3.34.
See all versions of @levo-so/next-middleware for other recorded verdicts.
- Review the evidence and your use of @levo-so/next-middleware@0.3.34 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.