finance/reporting

Release historydanger

The package is about 507 days old, with four releases clustered within roughly 4 hours and no releases in the last 12 months. That pattern provides little evidence of ongoing maintenance.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, reinforcing the absence of recent registry releases and raising abandonment risk.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. Although name differences can be normal for subpackages, the complete lack of identification weakens provenance confidence.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. This is a hygiene gap rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy. This is not severe alone, but it leaves vulnerability-reporting and response practices undocumented for a package handling financial data.