Is near-runtime-fees safe to use?

near-runtime-fees has no known vulnerabilities on the latest version (2.2.0). DepScope rates its health at 43/100 (high risk).

What is the latest version of near-runtime-fees?

The latest version of near-runtime-fees is 2.2.0, released 2020-09-03.

Does near-runtime-fees have known vulnerabilities?

No known vulnerabilities on the latest version of near-runtime-fees.

Is near-runtime-fees deprecated?

No, near-runtime-fees is actively maintained. Latest release: 2.2.0 (2020-09-03).

What are alternatives to near-runtime-fees?

Popular alternatives to near-runtime-fees in Cargo include: hashbrown, getrandom, windows-sys, syn.

What license does near-runtime-fees use?

near-runtime-fees is licensed under Apache-2.0.

near-runtime-fees

cargov2.2.0

Fees applied to near runtime encapsulated in a separate crate. Might merge it later.

License Apache-2.0permissive24 versions0 deps3,847 weekly dl

nearprotocol/nearcore

/ 100

Health

safe to use

[email protected] is safe to use (health: 43/100)

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cargo/near-runtime-fees