astermd/sdk

This is a promising but very young package: it has only two releases over 28 days and remains at v0.0.2, so API and maintenance stability are not yet established. The linked organization-owned repository is active, correctly associated with the package, includes tests, changelog, security policy, CI/release workflows, and dependency scanning, while the artifact is licensed and has no install-time scripts. The main concerns are that only one maintainer has published the package and one contributor made all commits in the last three months; adoption is also unproven with zero stars and forks. It is reasonable for early adoption with appropriate version pinning, but it is not yet a mature low-risk dependency.

Latest v0.0.2

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health checks

Maintainers

Only one registry account, AsterMD, has publish access. This is a concentration risk, although the organization-owned repository provides some potential maintenance continuity.

Release history

The package is only 28 days old with two releases and a median release interval of about 29 days. This is too little history to demonstrate mature stability, though the recent second release shows ongoing development.

Repo bus factor

One contributor accounts for 100% of the commits in the last three months, creating a high individual concentration risk. Organization ownership partly mitigates handoff risk, but no second active contributor is shown.

Repo commit activity

Only one commit was recorded in the last three months from one active maintainer. The very recent repository push and recent merged pull requests are encouraging, but the measured commit history remains thin.

Repo popularity

The repository has zero stars, forks, and watchers, so there is no community adoption evidence. For a package only 28 days old, this is a concern about maturity rather than a severe defect.