Is internal-russh-forked-ssh-key safe to use?

internal-russh-forked-ssh-key has no known vulnerabilities on the latest version (0.6.18+upstream-0.6.7). DepScope rates its health at 68/100 (moderate risk).

What is the latest version of internal-russh-forked-ssh-key?

The latest version of internal-russh-forked-ssh-key is 0.6.18+upstream-0.6.7, released 2026-02-28.

Does internal-russh-forked-ssh-key have known vulnerabilities?

No known vulnerabilities on the latest version of internal-russh-forked-ssh-key.

Is internal-russh-forked-ssh-key deprecated?

No, internal-russh-forked-ssh-key is actively maintained. Latest release: 0.6.18+upstream-0.6.7 (2026-02-28).

What are alternatives to internal-russh-forked-ssh-key?

Popular alternatives to internal-russh-forked-ssh-key in Cargo include: hashbrown, getrandom, windows-sys, syn.

What license does internal-russh-forked-ssh-key use?

internal-russh-forked-ssh-key is licensed under Apache-2.0 OR MIT.

internal-russh-forked-ssh-key

cargov0.6.18+upstream-0.6.7

Pure Rust implementation of SSH key file format decoders/encoders as described in RFC4251/RFC4253 and OpenSSH key formats, as well as "sshsig" signatures and certificates (including certificate validation and certificate authority support), with further support for the `authorized_keys` and `known_hosts` file formats.

License Apache-2.0 OR MITpermissive17 versions0 deps669,408 weekly dl

Eugeny/RustCrypto-SSH/

/ 100

Health

use with caution

[email protected]+upstream-0.6.7 low health (68/100) — consider alternatives

Moderate health score (68/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

14/20

popularity

25/25

security

9/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/internal-russh-forked-ssh-key