assert-no-unexpected-changes
github.com/yuyuyuyuyu-dev/assert-no-unexpected-changes- Category
- Developer Tools
- Rank
- No. 3060Tools index
Previous survey · No. 2894 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Software Testing & Quality
- Interfaces
- Host Plugin
- Latest release
- v1.0.0
- Date
About
A GitHub Action that asserts a desktop app, CLI tool or other program makes no unexpected changes, treating it as a black box. The author built it to check that code written by AI does nothing strange, and it runs as a step in CI workflows.
At a glance
This GitHub Action compares the filesystem changes in two Docker containers, one of which runs the command under test. It is worth adding to a Linux test workflow if your app should write only to a short, known list of paths.
Good fit
Developers checking for persistent file creation, deletion or modification outside approved paths.
Consider something else when
Use separate checks if you need to detect network requests, transient writes or behavior on macOS and Windows.
Start here
Use a fixture command that creates one expected file and one unexpected file outside the configured work directory. Allow only the expected path and confirm that the unexpected path appears in the failure.
Cost and requirements
MIT-licensed. It requires a Linux runner with Docker. The documented base image needs to run as root to change the copied workspace.
Limits to know
The action compares Docker filesystem diffs at the end of each run. Changes under the configured work directory are excluded, and the comparison cannot establish that an executable is safe.
Sources checked 2026-11-05. Source-based assessment.
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.