npmpackage.info

Gathering detailed insights and metrics for microtime

Other packages similar to microtime

relative-microtime

2.0.0

Get the number of microseconds elapsed since January 1, 1970 00:00:00 UTC without fear of clock drift

@types/microtime

2.1.2

TypeScript definitions for microtime

microtime-x

1.1.0

Get current time in microseconds (cross-environment)

microtime-nodejs

1.0.0

Native Javascript shim for the microtime (https://github.com/wadey/node-microtime) package

Gathering detailed insights and metrics for microtime

microtime - 3.1.1 | npmpackage.info

microtime

Get the current time in microseconds

3.1.1

603

MIT

C++

2.62 MB

4.5

Installations

npm install microtime

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Min. Node Version

>= 14.13.0

Node Version

14.19.3

NPM Version

8.12.1 Score

95.6

Supply Chain

79.7

Quality

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

6

Total

28

Closed

11

Merged

11

Issues

Open

3

Total

54

Closed

51

Releases

v3.1.1

Updated on Aug 12, 2022

v3.1.0-test-linux-arm64-build

Updated on Aug 11, 2022

v3.1.0

Updated on Jun 09, 2022

v3.0.0

Updated on Feb 04, 2019

v3.0.0-1

Updated on Jan 31, 2019

v3.0.0-0

Updated on Jan 28, 2019

View All 15 releases

Languages

C++

Python

JavaScript

C++ (60.55%)

Python (22.77%)

JavaScript (16.68%)

Developer

wadey

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

603 Stars

193 Commits

45 Forks

12 Watchers

24 Branches

8 Contributors

Updated on Jun 25, 2025

Maintainers

View All 8 Contributors

Package Meta Information

Latest Version

3.1.1

Package Id

microtime@3.1.1

Unpacked Size

2.62 MB

Size

827.61 kB

File Count

NPM Version

8.12.1

Node Version

14.19.3

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

node-addon-api node-gyp-build

Dev Dependencies

clang-format node-gyp prebuildify prebuildify-ci prebuildify-cross standard

node-microtime

Date.now() will only give you accuracy in milliseconds. This module calls gettimeofday(2) to get the time in microseconds and provides it in a few different formats. The same warning from that function applies: The resolution of the system clock is hardware dependent, and the time may be updated continuously or in ``ticks.''

N-API Support

As of version 3.0.0, this library is built using the N-API library. This should allow you to upgrade to newer versions of Node.js without having to reinstall / rebuild this library.

Version 3.0.0 and later also bundle prebuilt binaries for common systems in the npm package itself. These will be used if the version of Node you are using supports N-API (>= v6.14.2), otherwise the binary will be recompiled on install.

Installation

npm install microtime

Usage

microtime.now()

Get the current time in microseconds as an integer.

microtime.nowDouble()

Get the current time in seconds as a floating point number with microsecond accuracy (similar to time.time() in Python and Time.now.to_f in Ruby).

microtime.nowStruct()

Get the current time and return as a list with seconds and microseconds (matching the return value of gettimeofday(2)).

Example

> var microtime = require('microtime')
> microtime.now()
1297448895297028
> microtime.nowDouble()
1297448897.600976
> microtime.nowStruct()
[ 1297448902, 753875 ]

Estimating clock resolution

Starting with version 0.1.3, there is a test script that tries to guess the clock resolution. You can run it with npm test microtime. Example output:

microtime.now() = 1298960083489806
microtime.nowDouble() = 1298960083.511521
microtime.nowStruct() = [ 1298960083, 511587 ]

Guessing clock resolution...
Clock resolution observed: 1us

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

9

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

2

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 0

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/wadey/node-microtime/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/wadey/node-microtime/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:53: update your workflow using https://app.stepsecurity.io/secureworkflow/wadey/node-microtime/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:66: update your workflow using https://app.stepsecurity.io/secureworkflow/wadey/node-microtime/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:68: update your workflow using https://app.stepsecurity.io/secureworkflow/wadey/node-microtime/release.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/release.yml:72: update your workflow using https://app.stepsecurity.io/secureworkflow/wadey/node-microtime/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/wadey/node-microtime/test.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/wadey/node-microtime/test.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/wadey/node-microtime/test.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:45: update your workflow using https://app.stepsecurity.io/secureworkflow/wadey/node-microtime/test.yml/master?enable=pin
Warn: npmCommand not pinned by hash: .github/workflows/release.yml:46
Warn: npmCommand not pinned by hash: .github/workflows/test.yml:25
Warn: npmCommand not pinned by hash: .github/workflows/test.yml:51
Info: 0 out of 9 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 1 third-party GitHubAction dependencies pinned
Info: 0 out of 3 npmCommand dependencies pinned

0

Fuzzing

Determines if the project uses fuzzing.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Signed-Releases

Determines if the project cryptographically signs release artifacts.

0

SAST

Determines if the project uses static code analysis.

Score

4.5

/10

Last Scanned on 2025-06-30

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More