stratoss/phalcon2rest

Phalcon2 project with OAuth2, JWT and rate limiting

Latest 1.0.0

Packagist

38%

Total Score

unhealthy

Risky: the only release is over 10 years old and the repository shows no recent maintenance.

Health Score Breakdown

Release history

This package has only one release, published over 10 years ago, with no releases in the last 12 months. That strongly suggests abandonment for a framework-based API dependency.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with a project that has received no recent maintenance.

Package file tree

The source tree includes an ssl/private.key file alongside application code. Even without judging maliciousness, checking in a private key is poor repository hygiene and increases adoption risk.

Project backing

The package and repository are owned by the same individual account, providing consistent ownership context but no broader organizational backing to compensate for the lack of activity.

Repo tooling

Composer is used for builds, but no security scanning tooling is configured. The missing scanning is a hygiene gap rather than proof of unsafe code.