@napi-rs/keyring

https://github.com/hwchen/keyring-rs Node.js binding via https://napi.rs

Latest 2.1.1

78%

Total Score

healthy

Active maintenance and solid packaging are offset by completely unpinned CI actions and limited repository security hygiene.

Health Score Breakdown

Project backing

The repository owner is an individual rather than an organization, so the concentrated contributor activity is not offset by clear organizational handoff capacity.

Repo bus factor

The top contributor made two-thirds of recent commits, but two additional contributors were active, limiting rather than eliminating concentration risk.

Repo tooling

The project uses TypeScript and npm tooling, but no security-scanning tools were detected; this is a repository hygiene gap rather than evidence of unsafe code.

Security policy

No repository security policy was found, reducing transparency about how vulnerabilities should be reported and handled.

Workflow audit

The only workflow was fully analyzed with no untrusted checkouts or script injection, and it scopes permissions at job level. However, all 20 action references are unpinned and the audit found a high-confidence adhoc package installation; the cache findings were low-confidence hygiene signals.