Is @browselang/parser safe to use?

@browselang/parser has no known vulnerabilities on the latest version (0.0.22). DepScope rates its health at 40/100 (high risk).

What is the latest version of @browselang/parser?

The latest version of @browselang/parser is 0.0.22, released 2024-02-17.

Does @browselang/parser have known vulnerabilities?

No known vulnerabilities on the latest version of @browselang/parser.

Is @browselang/parser deprecated?

No, @browselang/parser is actively maintained. Latest release: 0.0.22 (2024-02-17).

What are alternatives to @browselang/parser?

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

What license does @browselang/parser use?

@browselang/parser is licensed under MIT.

@browselang/parser

npmv0.0.22

Parser for Browse using the ohm parser generator

License MITpermissive22 versions2 maintainers1 deps91 weekly dl

windsorio/browse

/ 100

Health

use with caution

@browselang/[email protected] low health (40/100) — consider alternatives

Moderate health score (40/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

ohm-js

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@browselang/parser