facturino/facturino-php

Repo bus factorcaution

All 15 recent commits came from one contributor, leaving no demonstrated backup maintainer. Organization ownership provides some handoff capacity, but the absent second active contributor remains a real continuity concern.

Repo popularitycaution

The repository has zero stars, forks, and watchers. This is weak supporting evidence for maturity, but popularity alone does not outweigh the active releases and recent commits.

Repo toolingcaution

Composer build tooling is present, but no repository security-scanning tool was detected. That is a transparency and maintenance gap, though it is not evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a genuine transparency gap for an API client.

Token permissionscaution

Neither workflow declares top-level token permissions. Although no workflow requests top-level write access, explicitly restricting permissions would provide stronger CI security hygiene.