mikycorp/apibundle

Release historydanger

Only two releases were published, both in May 2017, with no releases in roughly nine years. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing no evidence of current maintenance.

Package scaffoldingcaution

The artifact includes a README, but it is only 11 characters long, and neither the package nor repository has tests or a changelog. Missing tests and changelog are normal packaging practice; the extremely limited README is the meaningful gap.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no additional evidence of an active user or contributor community.

Security policycaution

The linked repository has no security policy, leaving no documented path for reporting vulnerabilities. This is a transparency and maintenance gap, though it is less severe than the inactivity evidence.