obviobysage/telemetry

The README, tests, MIT declaration, and organization-backed repository provide useful maintenance and integration evidence. However, the project has had no commits or releases for about two years, lacks security scanning and a security policy, and uses three unpinned workflow actions.

Latest 11.3.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package published 13 releases in about one week but none in the last 12 months; with the latest release roughly two years old, this indicates a substantial maintenance gap.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the roughly two-year gap since the last push and raising abandonment risk.

Repo popularity

The repository has zero stars and forks and only one watcher, showing very limited visible adoption. Popularity is supporting evidence rather than a verdict, so this modestly lowers confidence in project maturity.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a package handling telemetry data, that is a meaningful hygiene gap.

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency weakness, though not evidence that the package is unsafe.