ameax/datev-extf

Documentation and packaging are solid, with tests, release notes, and a matching MIT license. Organization backing and a focused dependency set help, but the project’s current maintenance capacity is uncertain.

Latest 1.1.0

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both clustered in March 2025, and none in the last 12 months. This materially raises maintenance-continuity risk despite the short initial release interval.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with a project whose latest activity was in March 2025. This weakens evidence of ongoing maintenance.

Repo issue activity

There are two open issues and one open pull request, with no issues or pull requests opened or closed in the last month. This adds evidence of limited recent project activity.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene concern rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, reducing transparency around vulnerability reporting and response expectations.