@noble/hashes

Maintainerscaution

Only one registry account has publish access. This is a concentration risk, though the repository shows that the same maintainer is actively producing releases and commits.

Project backingcaution

The repository is owned by an individual rather than an organization, so the concentrated maintainer and contributor activity is not offset by visible organizational handoff capacity.

Repo bus factorcaution

One contributor made all 48 commits in the last 3 months, creating a meaningful continuity risk if that maintainer becomes unavailable.

Repo toolingcaution

The project uses TypeScript and npm build tooling, but no security-scanning tools were detected. The repository still provides tests, an audit record, and a security policy as compensating transparency signals.

Token permissionscaution

Two of three workflows lack top-level permissions declarations, which is weaker workflow hardening; none declares top-level write permissions, limiting the severity of this gap.