some suggestions

[jimmywarting]

• Replace axios \w fetch
• use native web crypto instead of node crypto
• use explicit path with extensions
• don't depend so much on NodeJS stuff, would like to one day be able to use it in Deno or Bun.js. and heck even in browsers too. start by replacing Buffer with Uint8Array
• try to switch to ESM-only
• replace uuid dependency with crypto.randomUUID()
• remove legacy stuff like forge

[Coolchickenguy]

I checked, and web crypto would be very difficult because some of the apis this library uses from nodejs crypto (like PEM type auto-detection) are not available in web crypto, so at a minimum that would mean a large re-write to support (or an extra dependency).

[steven-tomlinson]

It sounds like you're saying the reason you're sticking with the poor decision to create a dependency on node.js is that it's too hard to fix?
The automatic PEM detection issue is not an issue. That's how it's supposed to work. Separation of concerns and maintaining a reduced attack surface, are all valid system design principles.

Just use an RSA compliant library or write a simple script to extract the 64-bit sig and handle it natively.
I'll let ChatGPT explain it more concisely.

CryptoJS was built for browser-based symmetric crypto. PEM and RSA are more complex and typically handled by libraries with ASN.1 and DER parsers—features CryptoJS lacks by design.

If you’re building a workflow that mixes symmetric and asymmetric crypto (e.g., AES for payload, RSA for key exchange), you might consider using CryptoJS for AES and jsrsasign or node-forge for RSA.

The reliance on node.js has dulled my enthusiasm for the project significantly over time.
Because of the dependency sprawl, broad attack surface, and related risks.
If you're concerned about the number of dependencies in SOLID, don't open that modules folder.

I honestly thought when I wrote the original setup guide, that the Node.js dependency was just a temporary hack. A quick MVP to demonstrate the principles behind SOLID.
I have been disappointed and concerned that the team ran with it ever since.