sgcsdk/sgcapi

The MIT license, included tests, and stable major version make the package straightforward to inspect and integrate. However, it has had no registry release since August 2019 and no recent repository commits, while the README is only 28 characters. The repository also does not clearly identify the package, lowering maintenance and ownership confidence.

Latest 1.1

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases exist, with the latest in August 2019 and none in the past 12 months. That long release gap is strong evidence of abandonment for an API library.

Repo commit activity

The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the multi-year release gap. The project is not archived, but its observed maintenance activity has stopped.

Repo package mention

The repository name does not match the package name and its README does not mention the package. That makes the source relationship and ownership less transparent.

Repo tooling

Composer is used as the build tool, but no security scanning tools are present. This is a modest repository hygiene gap alongside the stronger maintenance concerns.

Security policy

The linked repository has no security policy. This is a transparency gap for a package that exposes API integrations, though it does not by itself show unsafe behavior.