bennetgallein/billomat-client

Release historydanger

Only one release exists, published about three years ago, with no releases in the last 12 months. This strongly suggests the package is no longer actively maintained.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.

Project backingcaution

The package is backed by a user-owned repository rather than an organization, so the small registry maintainer count provides limited evidence of maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. This modestly reduces assurance, while tooling absence alone does not establish a maintenance failure.

Security policycaution

The repository has no security policy, so vulnerability-reporting expectations and security maintenance practices are not documented. This is a transparency gap, though not as severe as the inactivity evidence.