Package Health/dcodegroup/laravel-myob-oauth

dcodegroup/laravel-myob-oauth

The README, MIT declaration, and exact-version release note make integration reasonably transparent. The organization-backed repository is not archived, but maintenance has gone quiet and its workflow uses three unpinned actions. No security policy adds a smaller transparency concern.

Latest 0.1.8

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published about two and a half years ago, with no releases in the last 12 months. This materially raises maintenance and abandonment concerns for a dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old latest release, this points to a real maintenance risk.

Repo popularity

The repository has one star and no forks, indicating limited adoption. Popularity is only supporting evidence, so this modestly lowers confidence in project maturity rather than determining the verdict.

Repo tooling

The project uses Composer, but no security scanning tools were detected. That is a transparency and maintenance gap, though it is not severe by itself.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a smaller transparency concern for an OAuth integration package.