kafkajs

Repo commit activitydanger

There were zero commits and zero active maintainers in the three months before collection. Combined with the long release gap, this is the strongest maintenance and abandonment concern.

Build provenancecaution

No build attestation, trusted publisher, or staged publishing evidence is present. This is a transparency gap for release origin, though it does not by itself establish that the package is unsafe.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no organizational backing signal to compensate for the thin current activity.

Release historycaution

The project has a long history and 299 releases, but there have been no registry releases in the last 12 months; the latest release was about three years and seven months before collection. This materially raises staleness risk.

Repo issue activitycaution

The repository still has 356 open issues and 62 open pull requests, but only one new issue and no merged pull requests were recorded in the last month, suggesting limited current responsiveness.