trafficcophp/bytebuffer

Release historydanger

Only 2 releases were published, with the latest over 10 years ago and none in the last 12 months. This is strong evidence of abandonment for a library receiving ongoing dependency updates.

Repo commit activitydanger

There were 0 commits and 0 active maintainers in the last 3 months. Combined with the last push being over 9 years ago, this indicates sustained inactivity rather than a brief lull.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a minor hygiene gap, not evidence of maliciousness or abandonment by itself.

Repository archivedcaution

The repository is not archived, which avoids the strongest abandonment signal, but it was last pushed over 9 years ago. Its unarchived status provides little evidence of active maintenance.

Security policycaution

The repository has no security policy. This is a transparency and response-capacity gap, although it is less significant than the package's prolonged inactivity.