Package Health/mediagone/small-uid-doctrine

mediagone/small-uid-doctrine

Recent releases show the project is still maintained, but repository activity has been absent for about 6 months and only one maintainer is listed. Testing, licensing, and package-to-repository alignment are solid; the missing security policy is a smaller transparency gap.

Latest 0.8.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, leaving little publishing redundancy. The linked repository and recent release provide some compensation, but a single-person maintainer base still increases continuity risk.

Project backing

The repository is owned by the same individual user namespace as the package rather than an organization. That matches the single-maintainer context and provides no additional organizational continuity.

Repo commit activity

No commits and no active maintainers were recorded in the last 3 months, despite a release about 6 months ago. This pause lowers confidence in ongoing maintenance and responsiveness.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools were detected. The missing scanning coverage is a modest hygiene concern rather than evidence of abandonment.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap for a library that handles database type integration.