ironeyeapi/ironeye

This is a newly published, stable v1.0.0 PHP client with clear MIT licensing, a linked organization-backed repository, minimal runtime dependencies, no install-time lifecycle scripts, and no detected dangerous workflow patterns. However, it has only one release and is zero days old, provides no tests or changelog in either the artifact or repository, has no security scanning or security policy, and its single CI workflow does not declare top-level token permissions. The evidence supports cautious adoption rather than treating the package as mature; reassess after observing sustained releases, maintenance activity, and test coverage.

Latest v1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package file tree

The repository contains a compact, coherent Composer package with source files, README, license, and CI configuration, but no test suite or changelog is visible in the complete 18-entry tree.

Package scaffolding

A README is present and documents the client, dependencies, and usage, but neither the artifact nor repository contains tests or a changelog. For a new API client, the absence of both reduces transparency and confidence in maintenance quality.

Release history

The package is zero days old with exactly one release and no release interval history, so there is no demonstrated maintenance track record yet.

Repo issue activity

There are no open issues or pull requests and no activity in the last month. Given that the repository is newly created, this is inconclusive but does not demonstrate an established support process.

Repo popularity

The repository has zero stars, forks, and watchers. Because the package is newly released, these counters provide little evidence either way rather than constituting a severe concern.