myqaa/opentok
A complete README, tests, changelog, and MIT licensing support adoption. The repository has no recent commits, no security policy, and all five workflow actions are unpinned.
58%
Total Score
75
88
50
Health Score Breakdown
The package has 34 releases but none in the last 12 months, and its latest release was about four years ago. This is meaningful abandonment risk for a production SDK.
There were no commits and no active maintainers in the last three months, indicating that development has effectively stopped rather than merely slowed.
The project uses Composer, Phing, and Box for build work, but no security scanning tools are present. The build structure is positive while the missing security tooling is a modest transparency gap.
The repository has no security policy, leaving vulnerability reporting and response expectations unspecified for an SDK that handles API credentials and network calls.
Both workflows were analyzed successfully and have no dangerous triggers, untrusted checkouts, or audit findings. However, all five action references are unpinned, which weakens build reproducibility and supply-chain hygiene.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Ankur Oberoi |
| Community contributors |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 firebase/php-jwt Version ^5.0 | — | — |
guzzlehttp/guzzle Version ~6.0|~7.0 | — | — |
johnstevenson/json-works Version ~1.1 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 13 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.