Documentation and organizational ownership provide useful context. However, the last release was over three years ago, with no recent commits, no license, and no security policy, making future fixes and legal use uncertain.
52%
Total Score
75
75
50
No declared license, license file, or detected repository license was found. This creates a real legal and transparency concern for dependents.
The latest release was published over three years ago, and there were no releases in the last 12 months. This is meaningful evidence of slowing maintenance, although the package has a stable 1.6.1 release.
There were no commits and no active maintainers in the last three months, consistent with the release history showing no release for over three years. This raises abandonment and future-fix risk.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of a broad support community.
The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning reduces assurance for a package exposing application and mobile APIs.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
open2/amos-expo Version ^1.1.0 | — | — |
open20/amos-core Version * | — | — |
open20/amos-admin Version * | — | — |
understeam/yii2-fcm Version ~0.1 | — | — |
2amigos/yii2-qrcode-helper Version 1.0.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.