I updated the URL to the repo itself, since it's actually mostly written in JS/TS... but as a completely separate language, it's otherwise borderline off-topic.
Edit: not knocking the tooling at all, which is pretty interesting. I've been a relatively heavy proponent of just using scripting language(s) and some unified libraries as much as possible for different ETL work... especially variations on data ingress/egress. Where it's sometimes easier to manage many different solutions for each resource over trying to create more complex tooling.
Thanks! The primary form is a npm library so it did seem relevant here, hope it is.
definitely agree on the main purpose, I'm just now playing with plaintext/fixed length for an ETL home made process to try to get a customer not to try something in cobol..
I do see some usage as a library/server though.