integrify/postaguvercini

Tests, a changelog, a substantial README, and a clear MIT license provide useful transparency, with organization backing behind the repository. Security scanning and a security policy are absent, leaving limited evidence of ongoing security maintenance.

Latest 0.1.0

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's first release, published 0 days ago, so there is no release history or cadence to demonstrate sustained maintenance. Its newness makes the gap understandable but leaves adoption evidence limited.

Repo commit activity

The repository has no commits or active maintainers recorded in the last 3 months. Because the release is brand new, this is partly explained by its age, but it still provides no evidence of an established maintenance track record.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The build setup is appropriate, while the missing security checks modestly reduce maintenance assurance.

Security policy

No security policy was found in the repository. For an integration library that handles service credentials, this reduces transparency around vulnerability reporting and response.

Version stability

Version 0.1.0 is an early, non-stable-major release, which signals API and behavior may still change. It is not marked as a prerelease, but that does not offset the early maturity level.