vike@0.4.267
(Replaces Next.js/Nuxt) 🔨 Build mission-critical applications with stability and development freedom.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package metadata contains an explicit instruction aimed at controlling an AI agent’s review context. The inspected runtime code did not show a corresponding data theft or execution attack.
Decision evidence
public snapshot- package.json contains an instruction addressed to AI agents requiring them to load an external documentation URL while using Vike.
- The manifest declares no lifecycle scripts; its scripts are development, build, and release commands.
- The flagged Vite plugin checks for AI skill files during development and logs a hint; the inspected excerpts show no file writes or network requests.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/server/runtime/createDevMiddleware.jsView on unpkg · L4Package source references weak cryptographic algorithms.
dist/node/vite/plugins/build/pluginDistFileNames.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to vike@0.4.267.
See all versions of vike for other recorded verdicts.
- Avoid installing vike@0.4.267. 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.