codicastudio/backup

Release historydanger

The package has only one release, published about six years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the stable 1.0.0 version.

Repo popularitycaution

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide no external adoption signal to offset the long inactivity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This is a meaningful maintenance and transparency gap, though it is not evidence of unsafe code by itself.

Repository archivedcaution

The repository is not archived, which preserves a path for future maintenance, but it was last pushed about six years ago and does not offset the inactive release history.

Security policycaution

The linked repository has no security policy. For a package handling backup operations, this reduces transparency around vulnerability reporting and maintenance expectations.