ojs/doi-bundle

Release historydanger

The latest release was in December 2016, with no releases in the past 12 months and only two releases overall. This indicates a long-abandoned release line, with no newer registry version to offset the gap.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the release history showing no activity for years. This materially increases abandonment risk.

Package scaffoldingcaution

The published artifact has no README, tests, or changelog. Missing tests and changelog are normal for published artifacts, but the lack of consumer-facing documentation is a real gap for a PHP integration bundle.

Repo package mentioncaution

The linked repository name does not match the package name, and no README package mention was found. That leaves some uncertainty about whether the repository is the package's primary project, despite the substantial matching-looking source tree.

Security policycaution

The linked repository has no security policy. This is not proof of a security problem, but it weakens the project's transparency and gives maintainers no visible process for handling vulnerabilities.