codezero/twitter

Release historydanger

The latest release was published over ten years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a library 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 indicating no observed maintenance capacity.

Repo issue activitycaution

Two issues remain open, with no issue or pull-request activity in the last month. This is a modest additional sign that maintenance has stalled.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene and transparency gap, not evidence of maliciousness.

Security policycaution

The repository has no security policy. For a package handling API credentials, this reduces transparency about how vulnerabilities should be reported.