renderingvideo/sdk
Usable with caveats: the release is well-scaffolded, licensed, tested, and backed by an organization, but it is effectively new with only two releases today and no demonstrated maintenance history. The repository also lacks a security policy and security scanning.
62%
Total Score
88
100
75
90
Health Score Breakdown
Only two releases exist and both were published today, so there is not yet evidence of sustained release maintenance or long-term stability.
No commits or active maintainers are recorded in the last three months, but the package is only zero days old and the repository was pushed today; the short history is the concern, not demonstrated collapse in maintenance.
The repository has zero stars, forks, and watchers. This is consistent with a newly published project and is supporting evidence only, but it provides no external maturity signal yet.
Composer build tooling is present, but no security scanning tools are configured. That leaves a meaningful transparency and maintenance-control gap for a package handling API credentials.
No security policy is present. For an SDK that communicates with an external API, the absence of a documented vulnerability-reporting path is a genuine transparency gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 RenderingVideo |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.5 | — | — |
psr/http-client-implementation Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 20 days ago
- Created
- 20 days 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.