sherpa-onnx-node

Maintainerscaution

Only one registry account, k2-fsa, has publish access, which concentrates publishing control. This is partly mitigated by the repository's broader active contributor base, but registry recovery and publisher continuity remain more dependent on that account.

Project backingcaution

The repository is owned by an individual GitHub account rather than an organization, so the concentrated contributor activity and single registry publisher are not offset by clear organization-level maintenance backing.

Repo bus factorcaution

The top contributor accounts for about 68% of the 113 recent commits, creating concentration risk. Still, 13 other contributors were active during the same period, so this is a caution rather than a severe abandonment signal.

Repo package mentioncaution

The linked repository name does not match the package name and its README does not mention sherpa-onnx-node, raising uncertainty about whether it directly backs this package rather than merely being a related or parent project.

Repo toolingcaution

The repository uses CMake, showing an established build system, but no security-scanning tools were detected, leaving a CI security-hygiene gap.