tyler36/deployment

The package includes tests, uses no install-time scripts, and has no runtime dependencies. Its long inactivity and missing license leave significant maintenance and reuse risks.

Latest 1.0.2

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last 3 months, consistent with the repository having been inactive for about 5 years and 3 months. This is strong abandonment evidence.

Project backing

The repository is owned by an individual account rather than an organization. This does not prove inadequate support, but it provides less visible backing than an organization-owned project.

Release history

The latest release was published about 5 years and 3 months ago, with no releases in the last 12 months and only three releases overall. This indicates a materially stale release cadence.

Repo tooling

Composer is used as the build tool, but no security-scanning tool is reported. The absence of scanning is a hygiene weakness rather than a standalone dependency blocker.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This adds a transparency gap alongside the broader maintenance concerns.