ocdladefense/mw-teaser

The repository matches the package and contains the expected source files, while Composer is used for builds. Its lack of tests, security scanning, and security policy leaves little evidence of ongoing quality assurance.

Latest v1.0

Packagist

34%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published nearly five years ago, with no releases in the last 12 months. That strongly suggests the package may be abandoned, although a small feature package can sometimes be complete after one release.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since its sole release. No provided maintenance signal compensates for this inactivity.

License

There is no declared license, license file in the package, or license file in the repository. This creates a real adoption and redistribution concern rather than a cosmetic metadata gap.

Package scaffolding

The package includes a README, but it is only 12 characters long and provides no meaningful consumer guidance; the absence of tests and a changelog is normal for a published artifact and is not counted against it.

Repo tooling

Composer is used as a build tool, which supports reproducible package structure, but no security scanning tool is configured. That weakens assurance for a package with otherwise limited quality evidence.