cartwryte/wrightyard

The MIT license, matching repository, and release notes make the package transparent enough to inspect. Its organization backing helps, but the project remains immature and lacks a security policy or automated security scanning.

Latest v0.0.1

Packagist

53%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published about 14 months ago, with no releases in the last 12 months. That leaves little evidence of an established maintenance cadence.

Repo commit activity

The repository recorded no commits and no active maintainers in the last 3 months. Combined with the single-release history, this raises maintenance and abandonment concerns.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this provides no independent sign of community adoption or review.

Repo tooling

Composer is used for the build, which is appropriate, but no security scanning tools are configured. That weakens automated maintenance hygiene for a package intended to support development environments.

Security policy

The repository has no security policy, leaving no documented channel or process for handling vulnerabilities. This is a transparency gap, though not evidence that the package is unsafe.