What you can learn from manifest.json
The manifest names the extension, declares its version and entry points, and lists the permissions it needs. It is the first file a browser reads, which makes it the most reliable public description of capability.
A viewer groups related fields so you do not have to remember the schema. It highlights missing required values, deprecated manifest versions and broad permissions.
- Name, version and description
- Manifest version and browser signals
- Required and optional permissions
- Host permissions and content scripts
- Background worker or scripts
- CSP, update URL and externally connectable origins
Related pages:manifest viewer hubManifest V3 permissions
Uploading only the manifest
A standalone manifest.json is accepted, but referenced scripts are not included. The report will show permissions and configuration without code findings for missing files.
For a complete analysis, upload the full CRX, XPI or ZIP. The analyzer locates manifest.json inside the package and scans the other text files.
Related pages:CRX file analyzerFirefox XPI analyzer
Do not judge from one field
A manifest can look harmless while a referenced script performs sensitive work. Conversely, a broad permission can be justified by a feature. Read the manifest together with the code findings, domains and publisher information.