Is @subsquid/util-naming safe to use?

@subsquid/util-naming has no known vulnerabilities on the latest version (1.3.0). DepScope rates its health at 47/100 (high risk).

What is the latest version of @subsquid/util-naming?

The latest version of @subsquid/util-naming is 1.3.0, released 2024-05-07.

Does @subsquid/util-naming have known vulnerabilities?

No known vulnerabilities on the latest version of @subsquid/util-naming.

Is @subsquid/util-naming deprecated?

No, @subsquid/util-naming is actively maintained. Latest release: 1.3.0 (2024-05-07).

What are alternatives to @subsquid/util-naming?

Popular alternatives to @subsquid/util-naming in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @subsquid/util-naming use?

@subsquid/util-naming is licensed under GPL-3.0-or-later.

@subsquid/util-naming

npmv1.3.0

Naming conventions for squid framework

License GPL-3.0-or-later8 versions2 maintainers2 deps12,497 weekly dl

subsquid/squid

/ 100

Health

use with caution

@subsquid/[email protected] low health (47/100) — consider alternatives

Moderate health score (47/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

9/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

11.0 KBminified

4.1 KB gzipped

2 direct dependencies

side effectsscoped

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

camelcase inflected

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@subsquid/util-naming