verifymycontent/sdk

All four workflow actions are unpinned, and the repository has no security policy or automated security scanning. The package is well documented, tested, licensed, and backed by an organization with a recent release.

Latest v2.5.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a narrow publishing base. The organization-owned repository provides some backing, so this is a modest concern rather than a severe risk.

Release history

The package has existed for about 3 years and 10 months with 16 releases, but only one release in the last year. That points to a currently slow release cadence, despite the latest release being recent.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Although a release was published recently, the lack of recent development activity raises maintenance risk.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is consistent with a quiet project but does not by itself prove abandonment.

Repo popularity

The repository has zero stars, two forks, and one watcher. This is weak supporting evidence, but popularity is not decisive for a small, organization-backed SDK.