swaggest/api-compat

Release historydanger

The package has four releases, but its latest release was nearly seven years ago and there were no releases in the last 12 months. This substantially raises abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was nearly seven years ago. There is no observed recent maintenance capacity.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, and one issue remains open. This supports the evidence of an inactive project, though issue volume is small.

Repo toolingcaution

The project uses Make and Composer, showing basic build structure, but it has no detected security scanning tools. That is a hygiene gap rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy. For an inactive package, this leaves no clear documented route for reporting vulnerabilities or coordinating fixes.