SYK.INIT
v2.0
PROTOCOL.ACTIVE
ENCRYPTED
SEKYURITI
PREPARING ENVIRONMENT
_

AUTHENTICATED POST-DEPLOYMENT CONTROL

NPM PACKAGE PROTECTION

R

Runtime protection for npm packages. Encrypt your source. Control distribution. The key never leaves the server.

SERVER-SIDE KEY • ZERO SDK • NPM COMPATIBLE

0

CLIENT KEY

1

COMMAND

PROTECTVERIFYDECRYPT
PROTECTVERIFYDECRYPT
PROTECTVERIFYDECRYPT
PROTECTVERIFYDECRYPT

That is the system. Now you control it.

TYPE

NPM PROTECTION

RUNTIME

NODE.JS

STATUS

ACTIVE

REGISTRY
THE DIFFERENCE

WITH REGISTRYPROTECTED
  • Source is encrypted
  • Key is server-side
  • Revocation is possible
WITHOUTUNPROTECTED
  • Source is readable
  • No key required
  • No control
THE SEQUENCE

01

PROTECT

Submit your package. Source is encrypted.

02

PUBLISH

npm publish as normal. Zero friction.

03

REQUIRE

Users require() your package. Decryption is automatic.

SECURITY

PROPRIETARY
ENCRYPTION

Multi-layer encryption. The source never exists unencrypted on disk.

SERVER-SIDE KEY

The key never touches the client.

RUNTIME DECRYPTION

Decryption happens at require() time. Automatic.

REVOCATION

Cut access at any time. Immediate.

NPM COMPATIBLE

Standard package.json. Normal require().

PRICING

All plans include unlimited packages. Billing resets monthly.

USAGE

Same API. Protected source.

Your users require() the package normally. No SDK. No configuration.

CONSUMER CODEJAVASCRIPT
// Normal require - works the same
const yourPackage = require('@your-org/protected-package');

// Use as documented
const result = await yourPackage.doSomething();