~/audit
Inspect the code your browser receives
Each production build publishes a SHA-256 manifest of its HTML pages and browser assets. It includes inline page scripts as part of each HTML file, plus the JavaScript bundles, stylesheets, fonts and other files in the asset directory.
Check a file
- Open the manifest and choose a file. Each entry gives its URL path, byte size and SHA-256 digest.
- Download that file from this site. Use the Hash Generator in file mode, or run
shasum -a 256 downloaded-file.js. - Compare all 64 hexadecimal characters with the manifest. A match identifies the same file bytes.
In DevTools, the Sources panel lets you read the downloaded scripts. Use its pretty-print control for minified code. Network shows what is requested while a tool runs; the same short check is available on every tool.
What a matching hash tells you
It identifies bytes, not safe behaviour. The manifest and files come from the same publisher, so this is not an independent security audit or a signed release. Save the manifest if you want to compare later builds. The source repository is currently private; published browser code can be inspected, but LocalFirstTools is not offered as an open-source project.
A successful offline test demonstrates that the tested operation can run locally. It does not prove how every future build will behave. Check Network as well, using sample data.
Built by Patrick, a developer in the Netherlands.