rpc-websockets

Build provenancecaution

No build attestation or trusted-publisher provenance is present, leaving publication integrity less transparent even though the package has an established release history.

Maintainerscaution

Only one account has registry publish access, creating a limited publishing base; the organization-owned repository provides some backing but does not remove the operational concentration risk.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, a meaningful maintenance concern despite the recent registry release.

Repo toolingcaution

The repository uses an explicit TypeScript and bundling toolchain, but no security scanning tools were detected, leaving a security-hygiene gap.

Security policycaution

The repository has no security policy, making vulnerability reporting and response expectations less clear for a network-facing library.