meteocontrol/vcom-api-client
Healthy and suitable to use, with some maintenance and security-process caveats. It has a long release history, regular recent releases, active repository ownership, tests, and a current non-archived source repository, but recent commits come from only one contributor and no security policy or scanning tools are reported.
82%
Total Score
67
100
94
83
Health Score Breakdown
All 2 recent commits came from one contributor. Organization ownership provides some handoff capacity, but no second active contributor is shown, so recent maintenance remains concentrated.
Only 2 commits were recorded in the last 3 months, which is modest activity for an actively released package. The recent release history partly compensates, but this still leaves some uncertainty about ongoing development depth.
Composer build tooling is present, but no security-scanning tools are reported. This is a process gap rather than evidence of unsafe code, and the package's regular releases and tests provide partial compensation.
The repository has no SECURITY policy, leaving vulnerability-reporting and response expectations unclear for consumers of this API client.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 meteocontrol GmbH |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.7.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 9 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.