grizz-it/micro-service

The MIT license, clear README, and minimal runtime dependency reduce adoption friction. The organization-backed project lacks a security policy and scanning, while its very small footprint limits evidence of resilience. Pin this version only if its limited maintenance fits your needs.

Latest 1.0.0

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published about four years ago, with no releases in the past 12 months. That is strong evidence of a dormant project and raises abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the lack of recent releases. No newer activity is provided to offset this maintenance concern.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are present. The missing scanning reduces confidence in ongoing maintenance hygiene.

Repository archived

The repository is not archived, which preserves a path for future maintenance, but its last push was about four years ago. The non-archived status only partly offsets the stale activity.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency and maintenance gap, though it is less severe than the inactivity evidence.