Is @f/elapsed-time safe to use?

@f/elapsed-time has no known vulnerabilities on the latest version (1.0.0). DepScope rates its health at 48/100 (high risk).

What is the latest version of @f/elapsed-time?

The latest version of @f/elapsed-time is 1.0.0, released 2016-02-03.

Does @f/elapsed-time have known vulnerabilities?

No known vulnerabilities on the latest version of @f/elapsed-time.

Is @f/elapsed-time deprecated?

No, @f/elapsed-time is actively maintained. Latest release: 1.0.0 (2016-02-03).

What are alternatives to @f/elapsed-time?

Popular alternatives to @f/elapsed-time in npm include: semver, ansi-styles, debug, minimatch, brace-expansion.

What license does @f/elapsed-time use?

@f/elapsed-time is licensed under MIT.

@f/elapsed-time

npmv1.0.0

Maintain a running counter of time elapsed from a certain point

License MITpermissive1 versions1 maintainers1 deps7,857 weekly dl

git://github.com/micro-js/elapsed-time

/ 100

Health

safe to use

@f/[email protected] is safe to use (health: 48/100)

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

0.3 KBminified

0.2 KB gzipped

1 direct dependencies

side effectsscoped

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

@f/timestamp

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@f/elapsed-time