webshr/core

Usable with caveats: the release is licensed, tested, documented, and backed by an active organization, but the project is young and shows no commits or active maintainers in the last three months. Limited popularity and missing security policy add maintenance and transparency concerns.

Latest 1.1.0

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 321 days old with three releases and a median interval of about 161 days, showing a real release history but limited maturity and a relatively slow cadence.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, a meaningful maintenance warning; the recent push and release provide some compensating evidence but do not establish sustained activity.

Repo popularity

The repository has zero stars, one fork, and zero watchers, indicating a very small user and contributor footprint. Popularity is supporting evidence only, but this increases uncertainty for a young package.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected, leaving a transparency and maintenance-control gap for a package intended to run in WordPress projects.

Security policy

The repository has no security policy, so users lack a documented channel and process for reporting vulnerabilities.