intifact/sdk

This is a newly published, actively evolving SDK with a stable MIT license, a substantial generated API surface, tests in both the artifact and repository, no deprecation, no install-time scripts, and recent activity from two contributors. However, it is only 2 days old with three releases, has no security policy or security-scanning tooling, has no established popularity or issue history, and relies on a single registry maintainer; these factors limit evidence of long-term maintenance and operational maturity. It is potentially usable, but adoption should include monitoring for breaking changes and maintenance continuity.

Latest v2.1.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account, Roger, has publish access, which creates some publishing continuity risk; this is partly offset by repository activity from two contributors.

Project backing

The repository owner is an individual user rather than an organization, so there is no organizational handoff or backing evidence to offset the small maintainer base.

Release history

The package is only 2 days old with three releases and a median interval of about 1.2 days, so release momentum is visible but long-term maintenance and stability are not yet demonstrated.

Repo tooling

Composer is used as a build tool, but no security-scanning tooling is configured, leaving a genuine security-process and maintenance-hygiene gap.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and response expectations for a package that handles API authentication and invoicing integrations.