JavaScript mod intelligence · local-first analysis
Identify mod names and metadata, inspect version clues, imports, Eaglercraft APIs, library dependencies, and compatibility risks. Every finding includes its evidence level.
Static analysis results
The whole file is scanned: declarations, version references anywhere in code/strings/comments, protocol numbers and version-specific code names are weighed separately. The mod's own version, loader and client build are listed as info rows and never counted as game versions.
Repeated clues are grouped into one entry. API usage is separated from likely installable libraries.
Files the mod registers through libraries such as AsyncSink, and where each one comes from. Embedded assets make no network request, so they are not compatibility warnings.
Static checks flag patterns worth reviewing. They do not execute or sandbox the mod.
Metadata is only trusted as a claim made by the file, not independently verified.
Expand a finding to see the exact line or pattern that triggered it.