npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

epochver

v1.0.0

Published

Time-based versioning using Unix epoch reference (years.days.seconds)

Readme

EpochVer

npm version Build Status License: MIT Test Coverage

A time-based versioning system using Unix epoch reference.

Format

years.days.seconds

Where:

  • years: Years since 1970 (Unix epoch)
  • days: Day of year (1-366)
  • seconds: Seconds since start of day in UTC

Installation

npm install epochver

Usage

JavaScript/TypeScript

const epochver = require('epochver');

// Get current version
const version = epochver.getCurrentVersion();
console.log(version); // e.g. "55.109.3600" (55 years since 1970, 109th day, 3600 seconds)

// Convert date to version
const date = new Date('2025-04-19T10:30:00Z');
const versionFromDate = epochver.dateToVersion(date);

// Convert version back to date
const parsedDate = epochver.versionToDate('55.109.37800');

// Compare versions
const comparison = epochver.compareVersions('55.100.0', '55.109.37800');
// Returns: -1 (first version is earlier than second)

CLI

# Install globally
npm install -g epochver

# Get current version
epochver current

# Convert date to version
epochver to-version "2025-04-19T10:30:00Z"

# Convert version to date
epochver to-date "55.109.37800"

# Compare versions
epochver compare "55.100.0" "55.109.37800"

Why EpochVer?

Unlike semantic versioning (SemVer), EpochVer is:

  • Unambiguous: Each version has exactly one corresponding moment in time
  • Sortable: Versions can be compared chronologically using simple string comparison
  • Automatic: No need to decide what constitutes a major/minor change
  • Informative: The version itself tells you when the software was released

API

dateToVersion(date?: Date): string

Converts a Date object to an EpochVer string. Uses the current date if none provided.

versionToDate(version: string): Date

Converts an EpochVer string back to a Date object.

getCurrentVersion(): string

Gets the current version based on the current time.

compareVersions(v1: string, v2: string): number

Compares two version strings. Returns -1 if v1 < v2, 0 if v1 === v2, 1 if v1 > v2.

Contributing

Please see CONTRIBUTING.md for details on how to contribute.

License

MIT