sver-compat

Release historydanger

The package has had only 2 releases, both in August 2017, with no releases in the last 12 months. This is a substantial maintenance concern for a dependency, though the repository was pushed more recently.

Repo commit activitydanger

There were 0 commits and 0 active maintainers in the last 3 months. Combined with the absence of registry releases since 2017, this indicates weak current maintenance.

Build provenancecaution

No build attestation or trusted-publisher information is present, so publication provenance cannot be independently established. This is a transparency gap, but not by itself evidence that the release is unsafe.

Project backingcaution

The repository is owned by an individual user rather than an organization, so project backing is relatively thin. This matters more alongside the lack of recent commit activity.

Repo popularitycaution

The repository has 2 stars, 0 forks, and 1 watcher. Low popularity is only supporting evidence, but it reinforces the limited external validation of this small project.