staiapps/tasador-de-coches

Release historydanger

There has been only one release, published nearly ten years ago, with no releases in the last twelve months. This is strong evidence of abandonment risk despite the repository not being archived.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this provides no external adoption signal to offset the lack of recent releases.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap rather than proof of unsafe code, and it matters more because maintenance evidence is weak.

Repository archivedcaution

The linked repository is not archived, which is a positive counterpoint to the very old release history. However, its last push was also nearly ten years ago, so this does not establish active maintenance.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds transparency risk for a package with no recent maintenance evidence.