uttamrabadiya/api-version-manager

Release historydanger

The latest release was 0.3.0 on January 8, 2024, and there have been no releases in the last 12 months despite the package being about 2 years and 9 months old. The short median interval reflects only three early releases and does not offset the prolonged inactivity.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the stale release history. This is the strongest evidence of current abandonment risk.

Project backingcaution

The registry namespace and repository are owned by the same individual account rather than an organization. This does not indicate a problem by itself, but it provides limited evidence of organizational backing for long-term maintenance.

Security policycaution

The repository has no security policy. This is a transparency and maintenance gap, but it is modest for a small package and does not outweigh the stronger inactivity concern.

Workflow auditcaution

Both workflows were analyzed with no detected dangerous sinks or audit findings, and neither grants top-level write permissions. However, all 4 action references are unpinned, leaving a modest reproducibility and workflow supply-chain hygiene gap.