dv-team/mcp-server

Usable with caveats: it is actively released, licensed, tested, and backed by an unarchived organization repository. The main concerns are that the repository does not identify this package, recent work comes from one contributor, and the project has little visible adoption or security process.

Latest 0.6.2

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made all 2 recent commits, concentrating current maintenance knowledge. Organization backing helps with handoff potential, but no second active contributor is shown.

Repo commit activity

Only 2 commits were recorded in the last 3 months, although activity is not absent and the repository was recently pushed. This is a thin maintenance signal for a package releasing frequently.

Repo package mention

The repository name does not match the package name and its README does not mention the package, creating a real concern that the linked source may not clearly correspond to this release.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of adoption provides little external confirmation of project maturity.

Repo tooling

Composer build tooling is present, but no security scanning tool is reported, leaving a modest transparency and security-process gap.