o2system/security

The repository has no tests, no security policy, and no security scanning, while its workflow uses two unpinned actions. It remains licensed, non-archived, and correctly linked to the package, but those positives do not offset the long maintenance gap.

Latest v1.7.15

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no releases in the last 12 months, and its latest release was about six years ago. The earlier median interval of about 23 days shows this is a prolonged stoppage rather than a naturally slow cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history's long period of inactivity.

Package scaffolding

The package includes a substantial README and the exact version has a GitHub release, but it has no tests or changelog. Missing tests is a meaningful maintenance gap for a security-focused library; the absent changelog is normal for the published artifact.

Repo tooling

Composer is used for the build, but the repository has no security scanning tools. That leaves a relevant protection gap for a package providing authentication, encryption, and filtering components.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and maintenance expectations for a security-focused package.