cnp/wp-nav-filters

The repository offers little security and identity context. The focused artifact keeps the dependency surface small, but consumer documentation is absent.

Latest v0.4

Packagist

32%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in about 10 years: its latest release was April 2016, with four releases overall and none in the past 12 months. This is strong abandonment evidence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the package's long release gap and leaving little evidence of ongoing maintenance.

Repo package mention

The repository name does not match the package name, and no README mention was collected. That weakens confidence that the linked repository is clearly the package's authoritative home.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.

Security policy

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. The small, old project provides no other collected security-process evidence to compensate.