sebastianfeldmann/camino

The package is small and clearly identified, with a matching repository, MIT licensing, tests, and only one runtime dependency. Maintenance appears stale: the last registry release was over four years ago and there were no commits in the measured three-month period; workflow action pinning and security-policy gaps add modest hygiene concerns.

Latest 0.9.5

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry publishing account is present. This is a limited publishing base, but the linked repository is owned by the same individual, so it is not evidence of an ownership mismatch.

Release history

The package has only five releases and no releases in the last 12 months; its latest registry release was over four years ago, which is a meaningful maintenance concern.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the measured three-month period, reinforcing the concern that maintenance has slowed or stopped.

Repo tooling

Composer is used for the build, but no security-scanning tools were detected. The missing scanning is a modest transparency gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations undocumented and modestly reducing project transparency.