andyvanee/synchroversion

The MIT declaration and clear README make the small codebase easier to evaluate. There is no test or security-scanning evidence, so future compatibility and maintenance are difficult to verify.

Latest 0.0.5

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest of only five releases was published in March 2018, and there were no releases in the last 12 months. This is strong evidence of abandonment risk despite the short early release intervals.

Repo commit activity

The repository had no commits and no active maintainers in the last three months, consistent with the release history showing no activity since March 2018. This materially lowers confidence in ongoing maintenance.

Maintainers

One registry maintainer is consistent with an individual project, but it also indicates a thin publishing and maintenance base with no demonstrated redundancy.

Repo popularity

The repository has 1 star, 0 forks, and 2 watchers, providing little independent evidence of community adoption or review. Popularity is supporting evidence, so this reinforces rather than determines the assessment.

Repo tooling

Composer is used as the build tool, which is appropriate for a Packagist package, but no security-scanning tooling is present. That leaves dependency and repository-risk checks less transparent.