grokability/massdriver

Usable with caveats: this is a very new v0 package with only two releases today, so its long-term maintenance is unproven. It has a matching organization repository, tests, documentation, and a license, but no security policy or scanning is evident.

Latest v0.2

Packagist

70%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package was first released today and has only two releases, which is too little history to establish maintenance reliability. The repository was also pushed today, so the lack of historical activity is expected for this newly published package.

Repo commit activity

There are no commits or active maintainers recorded in the last three months, but the package and repository were created today. This is insufficient historical evidence rather than proof that maintenance has collapsed.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. For a newly published small package this is a genuine transparency and maintenance gap, though it is not by itself evidence that the package is unsafe.

Security policy

The repository has no security policy. That weakens vulnerability-reporting transparency, although the project is newly created and otherwise has a matching repository with visible tests and source files.

Version stability

The latest version is v0.2 and is not a stable major release, indicating an early-stage API that may change. It is not marked as a prerelease, which partially reduces the concern but does not provide much maturity evidence.