Is @openagenda/verror safe to use?

@openagenda/verror has no known vulnerabilities on the latest version (3.2.0). DepScope rates its health at 66/100 (moderate risk).

What is the latest version of @openagenda/verror?

The latest version of @openagenda/verror is 3.2.0, released 2026-02-09.

Does @openagenda/verror have known vulnerabilities?

No known vulnerabilities on the latest version of @openagenda/verror.

Is @openagenda/verror deprecated?

No, @openagenda/verror is actively maintained. Latest release: 3.2.0 (2026-02-09).

What are alternatives to @openagenda/verror?

Popular alternatives to @openagenda/verror in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does @openagenda/verror use?

@openagenda/verror is licensed under MIT.

@openagenda/verror

npmv3.2.0

richer JavaScript errors

License MITpermissive21 versions2 maintainers4 deps4,394 weekly dl

OpenAgenda/verror

/ 100

Health

safe to use

@openagenda/[email protected] is safe to use (health: 66/100)

Health breakdown0 – 100

20/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

7.5 KBminified

2.5 KB gzipped

4 direct dependencies

ESMscoped

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (4)

assertion-error depd inherits sprintf-js

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@openagenda/verror