betocampoy/champs-certificate

Project backingcaution

The repository owner matches the registry namespace, and the package is not relying on an unrelated organization repository. It is user-owned rather than organization-backed, so long-term continuity depends on a single visible owner.

Release historycaution

This is a young package, about five months old, with only one release and no demonstrated release cadence, so its maintenance maturity remains unproven.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, which is concerning for a package with only one release and provides little evidence of ongoing maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected, leaving a gap in repository hygiene for certificate-processing code.

Security policycaution

The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.