daverandom/async-bitly-client

Release historydanger

The latest release was published in October 2016, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment for a package still being considered as a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in October 2016. This materially raises abandonment risk.

Package scaffoldingcaution

The package includes a README, while tests and a changelog are absent in both the artifact and repository. Missing tests and changelog reduce transparency and verification for a library, though the README provides basic usage context.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked repository clearly represents this release.

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 meaningful sign of an active user or contributor base.