contenir/contenir-errors

The package is well documented, licensed, tested in its repository, and backed by an organization. Its maintenance history is too new to establish staying power, and the workflow passes inherited secrets with an unpinned action.

Latest v2.1.0

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 0 days old, with all 4 releases published within the same day and no established long-term release pattern. This limits evidence of sustained maintenance rather than indicating abandonment.

Repo commit activity

There were 0 commits and 0 active maintainers in the last 3 months, so there is no demonstrated maintenance history beyond the current release activity. The recent repository push and 4 merged pull requests provide some immediate activity but do not establish durability.

Repo tooling

The repository uses Composer build tooling, but no security scanning tools were detected. For a small PHP library this is a hygiene gap, not a standalone dependency blocker.

Security policy

No security policy was found in the repository. This reduces transparency for reporting vulnerabilities, although the package's small scope and test coverage partly limit the concern.

Workflow audit

The single workflow was fully analyzed with no untrusted checkout or script-injection path, and it has no top-level write permissions. However, it uses inherited secrets in a reusable workflow with high-confidence medium severity, and its only action reference is unpinned.