I’m Borewit. I build and maintain open-source libraries that help developers read music metadata, identify file formats, and process binary data efficiently.
The result is reusable infrastructure: an application can read an album’s tags and cover art, identify a file from its contents, or inspect a remote file without downloading every byte. Developers can build on these libraries instead of implementing the same format details themselves.
Source: npm download counts. Totals include dependency and automated downloads, so they do not represent unique people or applications. One installation can download several of these packages.
From libraries to working software
What this work makes possible
01
Read audio metadata across formats and environments
music-metadata extracts tags, cover art, duration, and technical audio information from formats including MP3, FLAC, MP4, Ogg, and WAV. It works with files and streams in Node.js and browser applications, giving developers one API across different formats and data sources.
Choose an audio file in the Audio Tag Analyzer to inspect its metadata and artwork directly in your browser. Your file stays on your device.
strtok3 provides a shared way to read binary data. With @tokenizer/http and @tokenizer/s3, parsers can read selected portions of remote files using range requests.
Metadata parsing and file detection can skip data they do not need to read. When the source supports range requests, this can reduce data transfer compared with downloading the entire file.
file-type identifies file formats from their contents. I help maintain this library, which uses the same tokenizer infrastructure and connects this work to applications beyond audio.
My file-type extensions add detection for audio and video, compound documents, PDF-based formats, and XML-based formats. I also contribute to is-svg.
A useful library needs continued care after its first release: investigating files that expose parsing bugs, adding regression coverage, keeping dependencies and runtime support current, and reviewing fixes and contributions.
Sponsorship helps me make time for that work across these shared libraries. A fix in a parser or tokenizer can benefit the applications that depend on it.
If your team relies on these projects, sponsoring their maintenance is a practical way to support the foundations of your own software. Individual support is welcome too.
Bug reports, reproducible sample files, documentation improvements, and pull requests also help these projects move forward. Thank you to everyone who contributes.
The wider toolkit
More of my work
These projects extend the same foundations into streaming audio, metadata services, file detection, and everyday development tools.
extracts tags, cover art, duration, and technical audio information from formats including MP3, FLAC, MP4, Ogg, and WAV. It works with files and streams in Node.js and browser applications, giving developers one API across different formats and data sources.
provides a shared way to read binary data. With @tokenizer/http and @tokenizer/s3, parsers can read selected portions of remote files using range requests.
identifies file formats from their contents. I help maintain this library, which uses the same tokenizer infrastructure and connects this work to applications beyond audio.