kloos/oc-chatwoot-plugin

The nine-file plugin has no tests, changelog, or README, and no security policy; those gaps make maintenance harder to verify. MIT licensing and only two runtime dependencies help, but do not offset the overall risk.

Latest 1.0.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in November 2020, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment risk for a dependency.

Package scaffolding

The artifact has no README, tests, or changelog. Missing tests and changelog are normal for published artifacts, but the missing README makes a small plugin harder for consumers to integrate and assess.

Repo issue activity

The repository has no open issues or pull requests and recorded no issue or pull-request activity in the last month. This supports the broader evidence of an inactive project.

Repo tooling

Composer is used for the build, but no security scanning tools are present. This is a modest transparency and maintenance gap, not evidence of a direct security problem.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This reduces maintenance transparency for a plugin that handles application integration.