Repository navigation
AutoFlowMate v0.4.1
AutoFlowMate is a free, open-source (MIT) automation tool for Windows PCs: files, Excel, PDF, Word, e-mail, web pages and any Windows program, built in a visual flowchart editor or recorded like a macro. This release hardens the privacy steps introduced in 0.4.0 (still beta).
Download
AutoFlowMate-v0.4.1-windows-x64.zip is a portable build with no installer. Unzip it anywhere and run autoflow-studio.exe. Keep autoflow.exe in the same folder.
To check the download: the .sha256 file holds its checksum, and the zip now carries a signed build-provenance attestation that proves it was built by this repository's release workflow from the tagged commit:
gh attestation verify AutoFlowMate-v0.4.1-windows-x64.zip --repo SRathinaGiri/AutoFlowMate
What's fixed and improved since 0.4.0
Redaction
- Existing outputs are no longer trusted without proof. In 0.4.0 a file already in the output folder was skipped when
overwritewas off, so an old or unredacted copy there could be passed on. Now the output folder keeps a manifest (.autoflowmate-redaction.json) with the SHA-256 of each input and output and a hash of the redaction settings. An existing output is reused (new statusunchanged) only when all three still match; anything else is redone. An interrupted run still continues where it stopped. - A file that fails is always removed from the output folder, including one left by an earlier run.
- Outputs are written to a temporary file and renamed into place, so an error or a stop never leaves half a file behind.
- Size limits keep one huge or malformed file from exhausting memory or disk: files over 1 GB, PDFs over 5,000 pages, pictures over 150 megapixels and Office files that unpack to over 4 GB fail (and are not written).
Pseudonymisation
- Token clash check: if a token is already in the vault for a different value, the step stops instead of reusing it (with 80-bit tokens this should never happen, but a token must never stand for two values).
- Fixed an integer overflow in the token encoder that stopped debug builds. Release builds, including 0.4.0, were not affected: the overflow happened after the token was complete. A fixed test now pins the exact tokens produced by 0.4.0, so vaults made with 0.4.0 keep working and tokens can't change unnoticed in future versions.
- AutoFlowMate's own code now keeps overflow checks on in release builds: such a bug stops with an error instead of silently giving a wrong value.
Release and supply chain
- Release zips carry a signed build-provenance attestation (see above).
- CI now also fails on dependencies with known security vulnerabilities or yanked versions (RustSec, via
cargo deny), next to the existing licence check.
Upgrading
Flows, tokens and vaults from 0.4.0 work unchanged. The first redaction run after upgrading redoes files already in an output folder once (there is no manifest yet to prove them).
Requirements
- Windows 10 or 11, x64. OCR uses the languages installed in Windows.
- Web actions need Microsoft Edge (preinstalled) or Google Chrome.
outlook_sendandoutlook_readneed classic Outlook.