Package Health/multilinguals/apollo-client

multilinguals/apollo-client

The small repository is clearly tied to the package, while its MIT license and README provide basic transparency. Missing security policy and scanning leave fewer safeguards for a package with limited project oversight.

Latest v0.1.2

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in December 2018, nearly eight years ago, and there were no releases in the last 12 months. This is strong evidence of abandonment for a dependency that may need compatibility fixes.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months, with the last push occurring over seven years ago. The lack of recent maintenance materially increases abandonment risk.

Repo issue activity

There were no new or closed issues or pull requests in the last month, despite eight open issues and one open pull request. Combined with the stale commit history, this suggests that reported problems are unlikely to receive attention.

Repo tooling

Composer is used as the build tool, but no security-scanning tools are configured. This reduces transparency around dependency and code risks without proving that the release is unsafe.

Security policy

The repository has no security policy. That leaves disclosure and response expectations unclear, although this is a secondary concern compared with the prolonged lack of maintenance.