foruzan/ms-sdk

Its MIT license, README, and changelog improve transparency, while the project has no security policy or scanning. The single maintainer and minimal adoption provide little evidence of ongoing support.

Latest v1.0.3

Packagist

43%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had four releases, all concentrated on November 22, 2021, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's prolonged release inactivity. There is no provided maintenance evidence to offset this.

Maintainers

The registry lists one maintainer, which leaves little apparent succession or review capacity when combined with the absence of recent activity. A single maintainer is not inherently unhealthy, but it increases abandonment risk here.

Repo popularity

The repository has zero stars and forks and only two watchers, indicating very limited adoption and little visible community support. Popularity is supporting evidence rather than decisive on its own, but it reinforces the maintenance concern.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. This is a transparency and hygiene gap, though it is less significant than the stale maintenance record.