Credentials in mapped fields
Checks mapper and parameter values, including named HTTP headers. Make connection references are not treated as embedded credentials.
Make scenario security · local export checker
A blueprint can carry mapped values and HTTP settings alongside the scenario structure. Review those settings before a handoff, a template release or a production change.
Check a Make exportFree · no signup · JSON stays on your device
Make blueprint JSON
Static analysis in a local browser worker
Download a report without secret values
Checks mapper and parameter values, including named HTTP headers. Make connection references are not treated as embedded credentials.
Checks HTTP modules for plain HTTP destinations, credentials in URLs and an explicit rejectUnauthorized: false setting.
Marks expression-based HTTP destinations for review. It does not assume that every mapped URL is attacker controlled.
The checker reads the JSON in this browser and analyzes it in a local worker. It does not upload the workflow, connect an account, contact its URLs or run its code. The checker route is excluded from VAS analytics and session replay.
No. It checks supported exported settings. It cannot verify connection permissions, platform or instance security, upstream gateways, arbitrary code behavior or runtime data flow. No findings is not a security certification.
Fixed finding descriptions, severity, review guidance and numeric workflow/step positions. Names, IDs, input paths, URLs, code, samples and credential values are omitted. Positions follow export traversal order and may differ from canvas numbering.
This checker reviews automation exports. The separate VAS integrations retrieve existing website-security reports inside an automation platform. Their availability and setup requirements are described on the integration pages.
Independently developed by Silex Dev. Platform names describe compatible export formats; they do not imply endorsement of this checker.