
Security News
Insecure Agents Podcast: Certified Patches, Supply Chain Security, and AI Agents
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.
Official implementation of the TypeID specification in TypeScript. TypeIDs are type-safe, K-sortable, and globally unique identifiers inspired by Stripe IDs
TypeIDs are a modern, type-safe, globally unique identifier based on the upcoming UUIDv7 standard. They provide a ton of nice properties that make them a great choice as the primary identifiers for your data in a database, APIs, and distributed systems. Read more about TypeIDs in their spec.
This is the official JavaScript / TypeScript implementation of TypeID by the jetify team. It provides an npm package that can be used by any JavaScript or TypeScript project.
Using npm:
npm install typeid-js
Using yarn:
yarn add typeid-js
Using pnpm:
pnpm add typeid-js
Note: this package requires Typescript > 5.0.0
To create a random TypeID of a given type, use the typeid() function:
import { typeid } from 'typeid-js';
const tid = typeid('prefix');
The prefix is optional, so if you need to create an id without a type prefix, you can do that too:
import { typeid } from 'typeid-js';
const tid = typeid();
The return type of typeid("prefix") is TypeID<"prefix">, which lets you use
TypeScript's type checking to ensure you are passing the correct type prefix to
functions that expect it.
For example, you can create a function that only accepts TypeIDs of type user:
import { typeid, TypeID } from 'typeid-js';
function doSomethingWithUserID(id: TypeID<'user'>) {
// ...
}
In addition to the typeid() function, the TypeID class has additional methods
to encode/decode from other formats.
For example, to parse an existing typeid from a string:
import { TypeID } from 'typeid-js';
// The prefix is optional, but it enforces the prefix and returns a
// TypeID<"prefix"> instead of TypeID<string>
const tid = TypeID.fromString('prefix_00041061050r3gg28a1c60t3gf', 'prefix');
To encode an existing UUID as a TypeID:
import { TypeID } from 'typeid-js';
// In this case TypeID<"prefix"> is inferred from the first argument
const tid = TypeID.fromUUID('prefix', '00000000-0000-0000-0000-000000000000');
The full list of methods includes:
getType(): Returns the type of the type prefixgetSuffix(): Returns uuid suffix in its base32 representationtoString(): Encodes the object as a string, using the canonical formattoUUID(): Decodes the TypeID into a UUID string in hex format. The type prefix is ignoredtoUUIDBytes(): Decodes the TypeID into a UUID byte array. The type prefix is ignoredfromString(str, prefix?): Parses a TypeID from a string, optionally checking the prefixfromUUID(prefix, uuid): Creates a TypeID from a prefix and a UUID in hex formatfromUUIDBytes(prefix, bytes): Creates a TypeID from a prefix and a UUID in byte array formatFAQs
Official implementation of the TypeID specification in TypeScript. TypeIDs are type-safe, K-sortable, and globally unique identifiers inspired by Stripe IDs
The npm package typeid-js receives a total of 246,363 weekly downloads. As such, typeid-js popularity was classified as popular.
We found that typeid-js demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.

Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.

Security News
The planned feature introduces a review step before releases go live, following the Shai-Hulud attacks and a rocky migration off classic tokens that disrupted maintainer workflows.