Borgmatic

Latest version: v1.8.11

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

Scan your dependencies

Page 12 of 28

1.4.16

Not secure
* 256: Fix for "before_backup" hook not triggering an error when the command contains "borg" and
has an exit code of 1.
* 257: Fix for garbled Borg file listing when using "borgmatic create --progress" with
verbosity level 1 or 2.
* 260: Fix for missing Healthchecks monitoring payload or HTTP 500 due to incorrect unicode
encoding.

1.4.15

Not secure
* Fix for database dump removal incorrectly skipping some database dumps.
* 123: Support for mounting an archive as a FUSE filesystem via "borgmatic mount" action, and
unmounting via "borgmatic umount". See the documentation for more information:
https://torsion.org/borgmatic/docs/how-to/extract-a-backup/#mount-a-filesystem

1.4.14

Not secure
* Show summary log errors regardless of verbosity level, and log the "summary:" header with a log
level based on the contained summary logs.

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.

Page 12 of 28

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.