Package Health

ride/web-cms-security

The MIT license, focused README, and organization-owned repository provide useful transparency. The lack of security tooling and security policy adds maintenance risk for a security-focused package.

Latest 1.1.0PackagistPackagist

40%

Total Score

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

50

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

79

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

83

Health Score Breakdown

Release historydanger

The latest release was over 7 years ago, with no releases in the last 12 months. Fifteen releases show some history, but the long inactive period materially raises abandonment risk.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months, consistent with the release history and indicating no current maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That is a meaningful hygiene gap for a security-focused package.

Security policycaution

The repository has no security policy. For a package explicitly providing CMS security widgets, this weakens vulnerability-reporting transparency and maintenance confidence.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Joris Vandeweerd

Direct Dependencies

DependencyLast ReleaseScore
ride/app
Version ^1.0.0
—
—
ride/web
Version ^1.0.0
—
—
ride/lib-cms
Version ^1.0.0
—
—
ride/web-cms
Version ^1.0.0
—
—
ride/lib-form
Version ^1.0.0
—
—

Weekly Downloads

Info

Last Published
7 years ago
Created
11 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