| Crates.io | srt-linter |
| lib.rs | srt-linter |
| version | 0.2.0 |
| created_at | 2025-05-09 19:28:09.415534+00 |
| updated_at | 2025-05-20 17:55:35.209204+00 |
| description | Look for issues inside SubRip text (.srt) files |
| homepage | |
| repository | https://github.com/furtidev/srt-linter |
| max_upload_size | |
| id | 1667520 |
| size | 953,288 |
srt-linter 💬🔍
💬🔍 srt-linter is a CLI tool to inspect and detect issues inside SubRip Text (.srt) files.
Install srt-linter with cargo:
$ cargo install srt-linter
If you don't have cargo or don't want to build srt-linter yourself, you can get the latest pre-built binary from here.
srt-linter has a very simple interface:
$ srt-linter --help
Look for issues inside SubRip text (.srt) files.
Usage: srt-linter [OPTIONS] <FILE_PATH>
Arguments:
<FILE_PATH>
Options:
-v, --verbose Logs additional information about internal actions
-s, --strict Enforces stricter rules for suspicious behavior
-t, --tui Shows a TUI at the end
-h, --help Print help
-V, --version Print version
Consider this:
$ srt-linter -s -v ./the.sopranos.s6.ep4.srt
[INFO] Detected BOM.
[SUCCESS] File is semantically OK.
[SUCCESS] File is structurally OK. Read 1565 line(s).
srt-linter is saying the following things:
U+FEFF) character on the file. (-v/--verbose)srt-linter says this file is valid. Let's load it up on a media player and see if srt-linter is right.
I'm using mpv and there you go:
A similar interface is available in srt-linter, just pass in the -t/--tui flag:
.srt format's unofficial markup extension.Hey, thanks! If you've found a bug or something that works unexpectedly, feel free to open an issue.
If you're a programmer and are interested in fixing it yourself, take a look at CONTRIBUTING.md. I really appreciate your help!
Thanks to @hitblast for helping me test srt-linter.
This project is licensed under the MIT license.