Package Health/vgen-apimatic/vgen-apimatic-sdk

vgen-apimatic/vgen-apimatic-sdk

This release is usable but immature rather than clearly unsafe to depend on. It has an MIT license, a substantial documented file tree, no install-time lifecycle scripts, an active non-archived organization-owned repository, and no registry deprecation. However, it is a newly published 0.0.1 package with only one release, no observed commit or maintainer activity beyond its initial publication, no tests or changelog, no security scanning, and no security policy. These gaps and the lack of demonstrated release history warrant caution until the project establishes maintenance and quality signals.

Latest 0.0.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a limited publishing continuity signal, though the organization-owned repository provides some backing context and registry access does not establish actual maintenance activity.

Package scaffolding

The package includes a substantial README, but neither the artifact nor repository contains tests or a changelog. For a newly generated API SDK, the documentation is useful, but the missing validation and release-history documentation remain maturity gaps.

Release history

The package is brand new: it is 0 days old and has only one release, so there is no demonstrated track record of maintenance or release stability.

Repo commit activity

The repository shows zero commits and zero active maintainers during the last 3 months. Because the package is newly created, this is more consistent with unproven maturity than confirmed abandonment, but it leaves maintenance capacity un demonstrated.

Repo tooling

Composer is used as a build/package tool, but no security scanning tools are present. The build setup is appropriate, while security-process coverage is limited.