synthigy/sdk

Documentation, licensing, repository tests, and a small dependency surface make the package straightforward to evaluate. It is only 11 days old, has three releases, and all recent commits come from one contributor. The unpinned workflow actions and missing security policy add maintenance and release-hygiene concerns.

Latest v0.2.0

Packagist

66%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 11 days old with three releases and a median interval of about 5.5 days. That shows active initial development but provides little evidence of long-term maintenance.

Repo bus factor

One contributor made all three recent commits, leaving no demonstrated individual redundancy. Organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo commit activity

There were three commits in the last three months and one active maintainer. Given the repository is only 11 days old, this is evidence of current work but not yet of sustained maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning layer is a release-hygiene gap rather than evidence of unsafe code.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented for a network-facing SDK.