swlib/saber

Release historydanger

The package has 22 releases and previously released every 15 days, but it has had no release in the last five years. That sustained pause materially raises abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the long release pause and weakening confidence in fixes or compatibility work.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while 31 issues remain open. This suggests limited current project responsiveness.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This is a maintenance and transparency gap, though the repository does include tests.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a genuine transparency gap for a network-facing HTTP client.