buble/sdk

The MIT license, clear README, test suite, and organization-backed repository provide a solid starting point. Missing security policy and scanning, alongside no commits in three months, leave maintenance and security assurance relatively thin.

Latest v0.1.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 116 days old and has two releases, both published on the same day. This is too little history to establish dependable maintenance, so it warrants caution.

Repo commit activity

There were zero commits and zero active maintainers in the past three months, despite the repository being only 116 days old. That leaves no observed ongoing maintenance after the initial release burst.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The build setup is appropriate, while security assurance remains limited.

Security policy

The repository has no security policy. That reduces transparency about vulnerability reporting and response expectations.

Version stability

Version v0.1.1 is a pre-1.0 release, which signals an early and potentially changing API. It is not marked as a prerelease, providing some counterweight but not maturity.