stellarwp/pipeline

Licensecaution

A license file is present, but the manifest declares GPL-2.0 while the artifact license file is detected as MIT. This mismatch creates a meaningful licensing and provenance question for downstream users.

Release historycaution

The package has had no release in more than two years and no releases in the last 12 months, which lowers confidence in ongoing maintenance. Its three releases were clustered at launch, suggesting a small or completed project rather than an actively evolving dependency.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months, consistent with maintenance having stopped for more than two years. For a library dependency, this raises abandonment and compatibility risk.

Repo toolingcaution

The repository uses Composer, but no security scanning tools were detected. For this small library, the missing scanner is a hygiene gap rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though it is less severe for a small, dormant library than an archived or deprecated package.