bscmain/bsc-php

Release historydanger

This is the only release, published about 15 months ago, with no releases in the last 12 months. That leaves little evidence of an established maintenance cycle.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with a repository that has seen no activity since the initial release. This materially raises abandonment risk.

Package file treecaution

The artifact contains a compact PHP SDK source tree and Composer metadata, but no consumer documentation is visible. The repository tree is similarly small and gives limited evidence of project maturity.

Package scaffoldingcaution

The published artifact has no README, tests, or changelog, while the source repository also reports no tests or changelog. The missing README is a meaningful integration gap for an SDK, though missing tests and changelog files are not expected in every published artifact.

Project backingcaution

The package namespace and repository owner are user accounts rather than an identified organization, and the signal provides no stronger project-backing evidence. Combined with inactivity, this gives limited confidence in ongoing support.