Developer tools
from ByBence.
Packages I build to solve recurring problems in real projects. The code, docs, limitations and benchmark notes live together here instead of being split across a marketing site and a README.
@bybence/securekit
Authenticated encryption for Node.js.
v0.9.0
AES-256-GCM, purpose binding, key rotation, blind indexes, sealed values, password hashing and a small CLI. No runtime dependencies.
runtime
Node.js >=20
license
MIT
token
sk4
runtime deps
0
npm i @bybence/securekit
view packageSecureKit keeps the application-facing side of encryption small.
The package is intentionally narrow: use Node's crypto primitives underneath, keep the repetitive framing, key handling and application conventions out of every feature that needs encrypted data.
usage.mjs
ESM
import { encrypt, decrypt } from "@bybence/securekit";
const email = "hello@example.com";
const token = encrypt(email, {
purpose: "user.email",
});
const value = decrypt(token, {
purpose: "user.email",
});The crypto primitive was not the hard part. The repeated application code around it was.
SecureKit packages the pieces that tend to get reimplemented differently from one field or service to the next: purpose separation, token framing, rotation checks, exact-match indexes and setup diagnostics.
No manifesto. Just a few rules I want the packages to follow.
This subdomain is meant to stay useful when there are more packages later, so the rules are about maintenance and clarity rather than one product's visual identity.
Small public APIs
A package should remove decisions from application code, not introduce a second framework to learn.
Trade-offs stay visible
Benchmarks, security boundaries and implementation assumptions belong next to the feature claims.
Dependencies have to earn their place
The default is to keep the runtime surface narrow and use platform primitives when they are enough.
bybence.co is for client work. This is where the reusable code lives.
ByBence builds custom websites and web systems. dev.bybence.co is the technical side of the same work: packages that are useful outside a single client project, published with enough documentation to stand on their own.
Visit bybence.co