Borgmatic

Latest version: v1.9.5

Safety actively analyzes 693883 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 14 of 29

1.4.13

Not secure
* Show full error logs at "--verbosity 0" so you can see command output without upping the
verbosity level.

1.4.12

Not secure
* 247: With "borgmatic check", consider Borg warnings as errors.
* Dial back the display of inline error logs a bit, so failed command output doesn't appear
multiple times in the logs (well, except for the summary).

1.4.11

Not secure
* 241: When using the Healthchecks monitoring hook, include borgmatic logs in the payloads for
completion and failure pings.
* With --verbosity level 1 or 2, show error logs both inline when they occur and in the summary
logs at the bottom. With lower verbosity levels, suppress the summary and show error logs when
they occur.

1.4.10

Not secure
* 246: Fix for "borgmatic restore" showing success and incorrectly extracting archive files, even
when no databases are configured to restore. As this can overwrite files from the archive and
lead to data loss, please upgrade to get the fix before using "borgmatic restore".
* Reopen the file given by "--log-file" flag if an external program rotates the log file while
borgmatic is running.

1.4.9

Not secure
* 228: Database dump hooks for MySQL/MariaDB, so you can easily dump your databases before backups
run.
* 243: Fix repository does not exist error with "borgmatic extract" when repository is remote.

1.4.8

Not secure
* Monitor backups with Cronhub hook integration. See the documentation for more information:
https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#cronhub-hook
* Fix Healthchecks/Cronitor hooks to skip actions when the borgmatic "--dry-run" flag is used.

Page 14 of 29

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.