iBrand auth api.
42%
Total Score
unhealthy
Risky: seven years without a release and six years without repository activity point to abandonment.
The latest release was in April 2019, with no releases in the last 12 months despite the package being over seven years old. This is strong evidence that the release line is abandoned.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push being about six years ago. The organization backing does not compensate for the lack of observed maintenance.
The repository has only 2 stars, 2 forks, and 1 watcher, providing little evidence of a broad user or contributor base. Popularity is supporting evidence, but this reinforces the abandonment concern.
Composer build tooling is present, but no security scanning tools were detected. That weakens ongoing assurance, especially for a package handling authentication-related functionality.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a transparency and maintenance gap for an authentication API package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ibrand/user Version ~1.0 | — | — |
ibrand/laravel-sms Version ~1.0 | — | — |
barryvdh/laravel-cors Version ^0.11.2 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.