baardbaard/bb-twitterfeed

Release historydanger

The latest registry release was over nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a package that integrates with an external service and WordPress.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, confirming that the long release gap reflects inactive development rather than a stable maintenance cycle.

Repo issue activitycaution

Seven issues remain open, with no new or closed issues and no merged pull requests in the last month. This adds evidence that reported problems are not being actively handled.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a hygiene gap, not evidence that the release is unsafe by itself.

Security policycaution

The linked repository has no security policy. That weakens the project's disclosure and response transparency, especially for a package that handles API credentials.