Is @openclawbrain/contracts safe to use?

@openclawbrain/contracts has no known vulnerabilities on the latest version (0.3.5). DepScope rates its health at 59/100 (high risk).

What is the latest version of @openclawbrain/contracts?

The latest version of @openclawbrain/contracts is 0.3.5, released 2026-03-22.

Does @openclawbrain/contracts have known vulnerabilities?

No known vulnerabilities on the latest version of @openclawbrain/contracts.

Is @openclawbrain/contracts deprecated?

No, @openclawbrain/contracts is actively maintained. Latest release: 0.3.5 (2026-03-22).

What are alternatives to @openclawbrain/contracts?

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

What license does @openclawbrain/contracts use?

@openclawbrain/contracts is licensed under Apache-2.0.

@openclawbrain/contracts

npmv0.3.5

Learning-first OpenClawBrain contracts, route_fn-aware validators, and checksum helpers.

License Apache-2.0permissive22 versions1 maintainers0 deps

jonathangu/openclawbrain

/ 100

Health

safe to use

@openclawbrain/[email protected] is safe to use (health: 59/100)

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@openclawbrain/contracts