gipfl/protocol-netstring

Release historydanger

Only two releases have been published, with no release in nearly six years and no releases in the last 12 months. This indicates a potentially abandoned package, though the stable release history does not show frequent churn.

Repo commit activitycaution

The repository has had zero commits and zero active maintainers in the last three months, consistent with the long release gap. That materially raises maintenance and abandonment risk.

Repo popularitycaution

The repository has zero stars and forks and one watcher, offering little community evidence to offset the inactive maintenance record. Popularity is supporting evidence only, so this is a secondary concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a dependency package, that is a modest transparency and maintenance weakness.

Security policycaution

The repository has no security policy. This leaves vulnerability-reporting expectations unclear, although the absence is a hygiene concern rather than evidence of an active vulnerability.