invoiceninja/inspector

Release historycaution

The package has existed for about 4 years, but only four releases and one release in the last 12 months indicate a slow release cadence. This is a maintenance concern, though not evidence of abandonment by itself.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. Despite the recent push timestamp, the measured development activity is currently weak and raises abandonment risk.

Repo issue activitycaution

There are six open issues, with no issues or pull requests opened or closed in the last month. This suggests limited recent project interaction, although the absence of open pull requests avoids evidence of an unmanaged backlog.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a real hygiene gap, though it is partly offset by the repository's tests and CI workflow.

Security policycaution

No repository security policy was found, leaving vulnerability-reporting expectations unclear. This lowers transparency but is not by itself evidence that the package is unsafe to use.