swaggest/swagger2-schema

Release historydanger

The latest release was about five years ago, with no releases in the last 12 months. This is strong evidence of inactivity for a package whose compatibility may need to track its ecosystem.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the roughly five-year gap since the last push. This materially raises abandonment and compatibility risk.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, and no work is currently queued. This is consistent with inactivity, though it does not independently prove the package is unusable.

Repo toolingcaution

The repository uses Make and Composer, showing basic build structure, but it has no security scanning tools. That weakens ongoing assurance, especially alongside the absence of recent maintenance.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, although it is less severe than the maintenance inactivity.