krzysztof-moskalik/api-client-bundle

Release historydanger

Only two releases were published on the same day, with no newer release for nearly eight months. That limited history and long pause provide weak evidence of ongoing maintenance.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, while the repository was last pushed nearly eight months ago. This is strong evidence that development has stalled.

Package scaffoldingcaution

The artifact includes a readable README, but it explicitly says the project is under construction and that not all features are implemented. Missing tests and a changelog are normal for a published package and are not counted against it.

Repo toolingcaution

Composer is used for the build, providing basic project tooling, but no security-scanning tool was detected. The missing scanner is a hygiene gap rather than proof that the release is unsafe.

Security policycaution

The repository has no security policy. That reduces disclosure transparency for a package handling API clients, although it is not by itself evidence of abandonment.