hamzz/voyager

Release historydanger

The package has 45 releases but none in the last 12 months, and its latest release was published over six years ago. This is strong evidence of abandonment risk for a framework integration package.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but that does not compensate for the absence of recent activity.

Project backingcaution

The registry namespace and repository owner match, but the owner is an individual account rather than an organization. This provides limited backing evidence and does not offset the lack of recent activity.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no external indication of an active user or contributor community.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanner is a transparency gap, partially offset by the repository's security policy and clean workflow audit.