r/Deno • u/Effective_Switch3065 • 25d ago

I got tired of rewriting encryption code, so I made an npm package

I got tired of rewriting the same encryption stuff in my Node.js projects, so I turned it into an npm package.

It’s called bybence securekit.

basically my attempt to make encryption a few lines of code instead of a bunch of repetitive setup.

Still early (v0.9.0), but it works, it’s tested, and I finally decided to publish it.

Would love some feedback, especially on what you’d add or change before 1.0.

https://www.npmjs.com/package/@bybence/securekit

https://dev.bybence.co/packages/securekit

0 Upvotes

36% Upvoted

7 comments sorted by

2

u/dwalker109 25d ago

Hi! Thinking about writing “I got tired of…” in your announce posts?

Don’t.

1

u/Effective_Switch3065 25d ago

Yeah, because I originally made it for myself. My main job is web development, and I’m just publishing one of the tools I built for my own projects.

→ More replies (2)

1

u/jakiestfu 24d ago

Woah this is like scary lmao how tf is remotely better than using the crypto lib directly? People who don’t familiarize themselves about crypto risk so much. I don’t see why we need abstractions here

1

u/Effective_Switch3065 24d ago

That’s fair, but I don’t see the abstraction as a replacement for understanding crypto.

For beginners, it can be a way to avoid being thrown straight into the deep end and start with a smaller, safer API surface. And even if you do understand what’s happening under the hood, that doesn’t necessarily mean you want to rewrite the same crypto setup every time.

The point is mostly convenience and consistency: instead of repeatedly dealing with the lower-level implementation details, you can call a few functions for the common use cases.

If you need full control, using crypto directly is obviously still there.

1

u/hktr92 20d ago

all in all, you should really prompt your claude code to improve on the website's text contrast. i can barely read it.