Package Health/opencontent/ocbootstrap-ls

opencontent/ocbootstrap-ls

This release appears usable and actively maintained: it has a long release history, a current stable version, a recent release, an unarchived organization-owned repository, recent commits from two contributors, and no install-time scripts or registry deprecation. However, transparency and maintenance confidence are reduced by the absence of tests and a security policy, very low repository adoption indicators, and the linked repository neither matching the package name nor mentioning the package in its README; verify the repository relationship and fit before adopting it for a critical dependency.

Latest 2.1.6

Packagist

72%

Total Score

Maintainer Stability

100

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README and changelog are present, but neither the artifact nor repository contains tests; for a substantial 966-file legacy design package, the absence of visible tests is a genuine maintenance and regression-risk gap.

Repo package mention

The repository name does not match the package name and its README does not mention the package, so the linkage is not independently corroborated and may indicate that the package is using a repository intended for something else.

Repo popularity

The repository has zero stars, two forks, and one watcher, so external adoption and review appear limited; this is supporting caution rather than evidence of abandonment because recent activity is present.

Repo tooling

Composer is used as a build tool, providing expected package tooling, but no security scanning tools are configured, leaving security hygiene less transparent.

Security policy

No repository security policy was found, reducing guidance and transparency for reporting vulnerabilities in a package that may be deployed in legacy web applications.