aplia/oworfilter

Its README, small seven-file tree, and Composer metadata make integration reasonably transparent. The organization-backed repository is not archived, but it lacks security scanning and a security policy, limiting confidence in ongoing care.

Latest v1.0.3

Packagist

56%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only four releases exist, with no release in the last 12 months; the latest was published in December 2021, nearly five years before collection. This is substantial evidence of inactivity for a dependency, though the stable version profile partly offsets release risk.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this indicates the project is currently inactive and raises abandonment risk.

Repo popularity

The repository has zero stars and one fork, so there is little public adoption evidence or community visibility. Popularity is supporting evidence only, but this reinforces the maintenance concern.

Repo tooling

Composer is used for builds, but no security scanning tools are present. That is a meaningful hygiene gap for a dependency, although it is not evidence of maliciousness by itself.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This reduces transparency for consumers of an already inactive package.