Package Health

cowegis/cowegis-core

This release is usable but warrants some caution. It is a stable, non-deprecated package with an identified organization-backed repository, an explicit LGPL license, a changelog, substantial source and specification files, Composer tooling, Dependabot, and no detected dangerous workflow patterns. However, its release history is sparse—only two releases across about 716 days with one release in the last 12 months—and the repository reports no commits or active maintainers in the last three months, which raises maintenance-continuity risk. The absence of a security policy and explicit workflow token permissions is also a transparency and CI-hardening gap, though there is no evidence here of repository archival or install-time lifecycle behavior.

Latest 1.1.0PackagistPackagist

68%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

88

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

89

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

80

Health Score Breakdown

Release historycaution

Only two releases have been published over about 716 days, with one release in the last 12 months; this sparse cadence limits evidence of sustained maintenance and lowers confidence in long-term continuity.

Repo commit activitycaution

The repository records zero commits and zero active maintainers over the last three months, despite a recent release and push timestamp. This weakens evidence of ongoing maintenance and creates abandonment risk.

Repo popularitycaution

The repository has zero stars and forks and one watcher. This indicates limited external adoption, but popularity is supporting evidence rather than a health verdict and does not by itself make the package unsafe to depend on.

Security policycaution

The repository has no security policy. This is a transparency gap for reporting vulnerabilities and coordinating security maintenance, with no provided compensating policy evidence.

Token permissionscaution

The sole workflow does not declare top-level token permissions. Although no write permissions were explicitly observed, the missing declaration is a CI hardening and transparency gap.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

David Molineus

Direct Dependencies

DependencyLast ReleaseScore
psr/container
Version ^1.0 || ^2.0
—
—
beberlei/assert
Version ^3.2
—
—
psr/http-message
Version ^1.0
—
—
psr/event-dispatcher
Version ^1.0
—
—
goldspecdigital/oooas
Version ^2.8
—
—

Weekly Downloads

Info

Last Published
24 days ago
Created
2 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform