Repository navigation
Releases
WAMF v0.4.3 – Security Maintenance Release
WAMF v0.4.3 Security Maintenance Release
WAMF v0.4.3 is a security maintenance release addressing embedded navigation URL validation and strengthening automated security regression testing.
This release incorporates the security fixes merged through PR #4 and the release preparation changes merged through PR #5.
It retains Python 3.11, the CPU TFLite classifier, existing application dependency pins and AMD64 deployment scope.
Changes
Security: Embedded Navigation (CodeQL #15)
Improved embedded navigation security by parsing link destinations using the browser's URL API and restricting permitted schemes to HTTP and HTTPS.
Unsafe or malformed destinations are rejected to prevent native clicks from executing potentially malicious URLs.
The fix preserves:
- Relative and internal navigation links.
- Fragment navigation.
- External HTTP/HTTPS links.
- Home Assistant
embed=hanavigation.
Security Regression Testing
Expanded automated regression coverage for:
- Permitted and rejected URL formats.
- Daily-summary and date navigation.
- Login redirects.
- Embedded navigation.
- Browser history behaviour.
Chromium CI Reliability
Updated browser testing to install the pinned Playwright 1.63.0 Chromium headless shell.
Affected command-line browser tests now prefer the headless shell, improving CI reliability while preserving existing security assertions and timeouts.
Test HTML Parsing (CodeQL #16–#18)
Replaced regex-based HTML extraction in security tests with Python's standard-library HTMLParser.
Additional tests cover tag and attribute case variations, HTML comments, quoted delimiters and preservation of inline JavaScript.
Upgrade Guidance
Stop WAMF cleanly before upgrading.
Back up configuration, database and media together, and retain the previous image or checkout for rollback.
Preserve existing:
- Volume mounts and storage paths.
- Network ports.
- Credentials.
- Session secrets.
No configuration, database or media migration is introduced in v0.4.3.
The local-build Docker Compose example uses:
wamf:0.4.3
The published container image is:
ghcr.io/wamf-project/wamf:0.4.3
For reproducible deployments, use the explicit version tag rather than relying on latest.
Refer to the repository's Docker testing and upgrade documentation for detailed instructions.
Retained Security Risks
The release security review on 28 October 2026 found no open GitHub CodeQL, Dependabot or secret-scanning alerts.
CodeQL alert #15 is closed.
This does not establish that WAMF or its dependencies are vulnerability-free.
Protobuf 3.20.3
Two known vulnerabilities remain:
These vulnerabilities are documented and their GitHub alerts have been dismissed as accepted risks, not patched.
TFLite Support 0.4.4 requires protobuf <4, preventing an isolated upgrade to the patched protobuf versions while retaining the existing dependency stack.
The existing compatibility-risk decision remains applicable.
Packaging and Setup Security
Previously documented packaging-tool and setup-token operational limitations remain.
Deployments should:
- Restrict access to startup logs.
- Disable setup request-body capture.
- Use HTTPS or a trusted tunnel for remote setup.
Runtime and Platform Limitations
Existing root-container, Flask runtime, Debian and native-library limitations remain.
The successful release validation does not establish that all underlying dependencies are free from vulnerabilities.
Validation
Automated Tests
The full Python 3.11 test suite completed successfully:
1,860 passed, 0 skipped
All release PR and post-merge pytest and CodeQL checks passed.
Version metadata was verified for consistency, and application dependency declarations remain unchanged.
Docker Image Validation
The v0.4.3 Linux/AMD64 release candidate was successfully built and tested in an isolated environment.
Validation confirmed:
- OCI image label reports version
0.4.3. - Runtime, administration interface and health API report version
0.4.3. - Web interface responds with HTTP 200.
- Authenticated health endpoint responds with HTTP 200.
- Unauthenticated health access correctly returns HTTP 401.
- Database and archive storage health checks pass.
- No unexpected startup errors occur.
The isolated smoke test did not exercise live Frigate or MQTT connectivity.
Temporary test resources were removed after validation, with existing containers, images, volumes and repository files preserved.
A separate v0.4.3 image-security scan has not been established by this validation.
Publication
Release tag: v0.4.3
Source commit: eb6d298
The tag-triggered Docker publishing workflow completed successfully.
The manual publishing workflow remains intentionally pinned to the historical v0.4.2 source and must not be used for v0.4.3 publication.
WAMF v0.4.3 is a security-focused maintenance release.
It introduces no new application features, configuration migrations or dependency upgrades.
Development of WAMF v0.5.0 Kingfisher continues separately.
WAMF v0.4.2
WAMF v0.4.2 maintenance release
Final planned v0.4 maintenance release, pending final release review and
publication. Retains Python 3.11, the existing CPU TFLite classifier and AMD64
deployment scope. No Kingfisher features or unrelated improvements are included.
Security fixes
- F-001: render detection values as DOM/text data rather than executable HTML
or inline handlers; validate Frigate event identifiers before ingestion,
requests, publication and archiving. - F-004: ignore spoofable forwarding headers for login throttling. Reserve
attempts before password verification and retain concurrent failures and active
overflow limits when dedicated capacity changes. - Harden Frigate media proxy paths, redirects, streaming cleanup and forwarded
headers; validate internal login destinations and bounded Wikipedia redirects. - Keep YAML source excerpts, credential-bearing exception text and unescaped
control characters out of the corrected responses and diagnostic logs.
First-run setup and interface
Fresh authentication-enabled installations print a private, single-use
/setup#token=... link instead of a temporary administrator password. Choose a
password within 15 minutes. Restarting pending setup invalidates the old link;
HTTP requests cannot renew it. Existing valid administrator/API credentials and
session secrets are preserved; malformed authentication configuration fails closed.
Operational workers pause until administrator setup completes and resume when
Frigate configuration is ready. Configuration updates use a lock and mode-0600
atomic replacement. Docker requires a writable configuration-directory mount.
The mobile navigation hamburger and collapse controls are restored.
Dependencies, Docker and browser assets
pytest is updated to 9.0.3. This release retains the constrained Python 3.11
runtime and Docker hardening from v0.4.1: reviewed base-image digest, build-time
Debian updates, dependency checking, removal of unused multimedia/OpenCV
components, and removal of pip, setuptools, wheel, packaging and ensurepip from
the merged runtime filesystem. These are carried-forward measures, not newly
verified v0.4.2 image results; removal does not erase inherited image layers.
F-005: Monaco Editor 0.52.2 is served locally, including its workers, with
the original MIT licence, third-party notices and checksum/provenance manifest.
The remaining external Bootstrap and jQuery tags use SHA-384 SRI and anonymous
CORS. See asset integrity details. Integrity does not provide
CDN availability or certify approved library versions as vulnerability-free.
Upgrade and retained risks
Stop WAMF cleanly and back up configuration, database and media together. Retain
the previous image and reuse existing mounts, ports and session-secret settings.
Existing provisioned v0.4.0/v0.4.1 installations require no data-format migration
or credential reset. Check login, API access, media, MQTT detection and restart
persistence after upgrading. See Docker upgrade instructions.
- Protobuf: retain the documented compatibility deferral for protobuf 3.20.3
and CVE-2025-4565/CVE-2026-0994. TFLite Support 0.4.4 requires protobuf below 4;
the trusted bundled-model boundary does not remove those vulnerabilities.
The existing risk decision remains
unchanged; no isolated major dependency upgrade is included. - F-006: retain the scoped local packaging-tool risk acceptance,
finalized for v0.4.2 on 2026-10-27. Local pip/setuptools advisories remain relevant
to package-management operations; no normal WAMF runtime path was identified. - F-007: retain the conditional setup-token risk acceptance,
finalized for v0.4.2 on 2026-10-27. Anyone with the unused startup link and network
access can set the administrator password. Restrict startup/centralized logs to
trusted administrators, disable setup request-body capture, and use HTTPS or
a trusted tunnel for remote setup. The printed loopback URL is not an access
control. - Existing root-container/Flask runtime, legacy credential compatibility and
Debian/native-library limitations remain; this is not a vulnerability-free
release claim. Historical image findings are documented in the
v0.4.1 security limitations.
Validation and release conditions
The consolidated pre-metadata audit passed 1,344 full-suite tests and 1,220
overlapping targeted security tests using .venv311, with no failures, skips or
warnings reported. It found no new actionable vulnerability or failing security
regression. Those results describe the audited source tree, not a newly built
v0.4.2 container.
Final release review must retain the F-006/F-007 acceptance conditions and include
the necessary currently untracked source, assets, tests and records in the release
artifact. Current-tree Docker build/runtime and image-security verification remain
outstanding. Registry tag 0.4.2 is usable only after publication; preparing these
notes and version metadata does not publish or approve the release.
WAMF v0.4.1 – Security Maintenance Release
Security and dependency maintenance
WAMF v0.4.1 is a security maintenance release for existing WAMF v0.4.x installations.
- Updated and constrained compatible Python dependencies, including Flask, Werkzeug, Requests, Pillow, certifi and urllib3.
- Updated the Python 3.11/Debian runtime base and reduced the container attack surface by removing unused FFmpeg, OpenCV and packaging tools.
- Preserved existing configuration, database and media formats, first-run provisioning, credentials and session secrets.
- Retained legacy Werkzeug credential compatibility following dependency updates, including legacy API-token verification and non-destructive startup validation.
Validation
- 411 Python 3.11 host tests passed.
- 406 container tests passed; five Node-dependent tests were skipped in-container and passed on the host.
- Upgrade and rollback testing passed without credential loss.
- Gitleaks and the Trivy critical-vulnerability gate passed in the publishing workflow.
- AMD64 deployment was validated on Bird-Watcher, including authentication, real Frigate MQTT events, CPU species classification, database persistence, snapshot and video clip archiving, Frigate sublabel updates, and persistence across container restart.
Known residual protobuf vulnerabilities
WAMF v0.4.1 retains protobuf 3.20.3 for compatibility with TFLite Support 0.4.4. CVE-2025-4565 and CVE-2026-0994 remain unresolved.
The affected pure-Python protobuf backend is active, including binary parsing of internally generated classification results. Security review found no application path allowing external inputs to supply arbitrary protobuf wire data, and no reviewed application path invoking the vulnerable protobuf JSON/Any parser.
These findings indicate limited exposure in the audited configuration, not elimination of the vulnerabilities. Users should continue using trusted classification models and controlled configuration.
Residual Debian scanner findings are documented in the repository security assessments. This release is not claimed to be vulnerability-free.
Container availability
ghcr.io/wamf-project/wamf:0.4.1
The ghcr.io/wamf-project/wamf:0.4 tag also tracks this maintenance release. Architecture: linux/amd64 (AMD64). ARM is not a supported deployment target for this release. WAMF classification runs on the CPU. The existing latest and 0.4.0 image tags are preserved.
See the release and upgrade guidance and validation report.
Immutable image reference:
ghcr.io/wamf-project/wamf@sha256:ca6c51fb1d90696bb758b753ce43aaecf71c5a7b4288d25b2a656b5bfc6b5040
WAMF model artifact: AIY Birds V1
Dedicated classification-model artifact release for WAMF Model Manager. This is not an application release and does not activate or select a model.
Asset: bird-aiy-v1.tflite (bird/aiy-v1)
- Size: 3,621,418 bytes
- SHA-256:
1dea79841cd7d767515c928ed5010ec49df57bef37aaa894f70b44eaa45d1cab - Runtime/contract: CPU LiteRT,
wamf-bird-v1, uint8[1,224,224,3]input and uint8[1,965]output.
Published by Google, sourced from the authoritative Coral CPU model. Upstream SHA-256: 350fcd8cf1df1560060d464595dfed8b174b05792788052896004848d9ad04f9.
Google's model-specific documentation explicitly licenses AIY Birds V1 under Apache 2.0. The licence and packaging/attribution notice are included as associated LICENSE and NOTICE files inside the asset.
All upstream bytes and weights are preserved. WAMF's existing embedded probability label files are added without reordering or remapping classes. Scientific names at indexes 110 and 758 use U+00D7, correcting literal backslash-x-d-7 text in Coral's labels; these names agree with Google's official label map. The original Coral associated label file is retained unchanged.
M1 size/hash/structural/label/background validation and synthetic inference smoke checks passed. Three deterministic inputs produced byte-identical outputs before and after packaging; this does not measure accuracy. Packaging was reproduced byte-for-byte using scripts/package_aiy_birds.py.
WAMF v0.4.0
WAMF v0.4.0
WAMF v0.4.0 is the first release in the WAMF release series, building on the original Who's At My Feeder project.
This release focuses on deployment portability, Docker support, first-run setup, reliable application lifecycle management, Frigate compatibility, and improved health monitoring.
Highlights
- Docker deployment support with persistent configuration, database, snapshots, and clips.
- First-run bootstrap and setup mode with automatic administrator credential generation.
- Admin configuration interface with controlled application restart.
- WAMF health monitoring and system health reporting.
- Proactive Bridge health monitoring with optional observation and health-state events.
- Frigate snapshot and clip archiving.
- Frigate sublabel updates following successful species classification.
- Native and Docker deployments now consistently use port 7767.
- Docker runtime targets Python 3.11.
Reliability and deployment improvements
- External configuration is validated before MQTT and classification workers start.
- Application paths are resolved consistently across native and Docker deployments.
- Shutdown and restart handling coordinates child processes before exit or re-execution.
- Docker uses persistent
/app/config,/app/data, and/app/mediapaths. - Fixed MQTT connection readiness reporting.
- Retained MQTT messages are no longer incorrectly treated as new detections.
- Fixed Docker packaging, bind-mount, storage-path, first-run configuration, and port issues.
- Added Docker packaging regression tests.
- Fixed test dependency installation drift.
Compatibility
WAMF v0.4.0 has been verified with:
- Frigate 0.17.2
- Frigate 0.18.0
- Ubuntu 24.04 native installation
- Docker cold bootstrap
- Live detection processing and media archiving
- Admin restart
- Persistence across container recreation
Container image
The official container image is available from GitHub Container Registry:
ghcr.io/wamf-project/wamf:0.4.0
The 0.4 and latest tags also point to this release.
WAMF originated from the Who's At My Feeder project. Releases prior to the current WAMF release series predate the WAMF changelog and have not been reconstructed.
WAMF v0.4.0-beta.3
Docker deployment validation release.
Highlights:
- Verified clean Python 3.11 environment
- Verified Docker image build
- Verified Docker runtime startup
- Verified fresh database creation
- Verified mounted data and media volumes
- Verified MQTT and Frigate connectivity from Docker
- Verified end-to-end detection pipeline in Docker
- Fixed fresh database homepage handling
- Fixed shared config loading for Docker runtime
Known remaining work:
- Bird-Watcher deployment validation
- Docker documentation
- Website and install docs
- MQTT reconnect backoff
v0.4.0-beta.2
Deployment portability improvements
- Database path now configurable
- Snapshot path now configurable
- Clip path now configurable
- Live view URL configurable
- Improved media path handling
- Removed legacy Frigate media mount dependency
- Additional test coverage
- Deployment preparation for Docker support
WAMF v0.4.0-beta.1
WAMF v0.4.0-beta.1
First public beta release of the Wildlife Activity Monitoring Framework.
Highlights
- Stable Bird-Lab deployment
- Systemd service support
- Wildlife observation management
- Species database
- Live camera integration
- Authentication and session security
- API token authentication
- Media retention policies
- Clip and snapshot cleanup
- Orphaned media detection
- Automated database cleanup
- Improved administration interface
- GitHub CI testing
Known Limitations
- Docker deployment not yet available
- Some file paths remain deployment-specific
- Admin navigation will continue to evolve
Next Steps
Development will now focus on:
- Deployment portability improvements
- Docker support
- Path abstraction and external media storage
- Additional documentation
- Preparation for full v0.4 release
Thank you to everyone following and testing the project.