| Version | Supported |
|---|---|
| 0.x.x | ✅ |
Do not report security vulnerabilities through public GitHub issues.
Instead, please report them via:
- Email: [YOUR-EMAIL]
- GitHub Security Advisory: Create a private advisory
Please include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
You will receive a response within 48 hours. We take all security reports seriously.
FilaOps is ONLY distributed through:
| Channel | URL | Verified |
|---|---|---|
| GitHub Repository | https://github.com/Blb3D/filaops | ✅ |
| GitHub Releases | https://github.com/Blb3D/filaops/releases | ✅ |
- ❌ Direct zip downloads from
raw.githubusercontent.com - ❌ Third-party websites
- ❌ Email attachments
- ❌ Discord/forum file shares
- ❌ Any other GitHub account
If you find FilaOps hosted elsewhere, it may be malicious.
All official releases include SHA256 checksums.
Linux/macOS:
# Download the release and SHA256SUMS.txt
sha256sum -c SHA256SUMS.txtWindows (PowerShell):
Get-FileHash filaops-vX.X.X.zip -Algorithm SHA256
# Compare output to checksum in SHA256SUMS.txtReleases are signed with GPG. To verify:
# Import public key (one-time)
curl -s https://raw.githubusercontent.com/Blb3D/filaops/main/PUBLIC-KEY.asc | gpg --import
# Verify signature
gpg --verify SHA256SUMS.txt.sig SHA256SUMS.txt
# If valid, verify checksums
sha256sum -c SHA256SUMS.txtKey fingerprint: [FINGERPRINT WILL BE ADDED]
We maintain awareness of malicious forks and distribution channels targeting our users.
| Repository | Status | Details |
|---|---|---|
printertechn/filaops |
🔴 MALICIOUS | Distributes malware via modified download links. Reported to GitHub. |
If you encounter a suspicious FilaOps fork or distribution:
- Do not download anything from it
- Open an issue with the URL
- Report directly to GitHub if it contains malware
As of January 2026, FilaOps implements:
- ✅ SHA256 checksums on all releases
- ✅ GPG-signed checksum files
- ✅ Automated release pipeline via GitHub Actions
- ✅ Security warnings in README
- ✅ Public security policy (this document)
- ✅ Monitoring of known threats
In the event of a security incident affecting FilaOps users:
- Security advisory posted to GitHub
- Affected versions clearly documented
- Mitigation steps provided
- Announcement in GitHub Discussions
- Security issues: [YOUR-EMAIL] or GitHub Security Advisory
- General questions: GitHub Discussions
- Maintainer: Brandan Baker (@Blb3D)
Last updated: January 18, 2026