Archer Laravel Package

Product Decisions This Supports

• Build vs. buy on internal test tooling. Archer is a reference implementation of "convention over configuration" for test discovery, fixtures, and doc generation. Its value to us is as prior art when scoping whether to build a bespoke test harness — read it, don't ship it.
• Technical debt triage / roadmap. Any service in the portfolio still declaring icecave/archer is a modernization ticket, not a feature enabler. Its presence is a concrete signal to schedule migration to PHPUnit/Pest and a standard CI pipeline.
• Testing standards and ADRs. The "tests, CI, and docs from one source" premise can inform an internal style guide or architecture decision record — e.g., generating API documentation from executable specifications.
• Vendor/OSS due diligence. A useful case study for how we score abandoned dependencies: single maintainer, dormant repo, no release cadence, zero dependents.
• What it does not support. With no stars recorded and zero dependents, it cannot de-risk a feature decision. The 10.75 "opportunity" score should be read as an ecosystem gap worth watching, not an adoption recommendation.

When to Consider This Package

Consider it only when:

• You are maintaining a pre-existing IcecaveStudios codebase that already depends on it and cannot be migrated this quarter — vendor the source, pin the version, add characterization tests, and plan the exit.
• You need a read-only reference for annotation-driven test generation or doc-from-tests design during an internal spike. Do not ship it.
• You explicitly accept: PHP 5.x-era runtime, no security patches, no PHP 8 compatibility, no community support, no license/provenance continuity guarantees.

Look elsewhere when:

• The project is greenfield or actively maintained → PHPUnit 10/11, Pest, Codeception; ParaTest for parallelism; GitHub Actions or GitLab CI for pipelines; phpDocumentor plus PHPStan/Psalm for docs and static analysis.
• You need supported CI integrations, coverage tooling, or modern PHP compatibility.
• Any requirement exists for security review, vendor SLAs, or maintenance commitments — a dormant single-maintainer repo fails all three.
• You are assessing dependency risk: zero stars and zero dependents make this the opposite of a de-risked dependency.

How to Pitch It (Stakeholders)

Executives: Archer is an abandoned, single-vendor PHP "test by convention" toolkit. No releases, no dependents, no support — it is not a candidate for adoption. Its only value is as prior art for a one-source-of-truth workflow across tests, CI, and documentation. Recommendation: no spend, no new dependency. If it appears anywhere in our portfolio, fund a small migration to PHPUnit/Pest with a standard CI pipeline.

Engineering: Do not add icecave/archer to any new project. If found in a legacy tree, treat it as tech debt: vendor the source, freeze the version, wrap it in characterization tests, and migrate to PHPUnit (or Pest) + GitHub Actions + phpDocumentor/PHPStan. Steal the convention-over-configuration ideas; do not depend on the code. Budget roughly one sprint per affected service, scaled to suite size.