mlsolutions/chart-js-integration

Maintainerscaution

Only one account has registry publish access, which creates a limited publishing succession path. The organization-owned repository provides some compensation, so this is a concern rather than a severe risk.

Release historycaution

The package has three releases, all within its first 8 days, but no release since February 27, about 7 months ago. That short burst followed by a long pause raises maintenance concern for a package still only about 7 months old.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the registry's lack of releases since February. This is a meaningful abandonment risk despite the project's recent origin.

Security policycaution

The repository has no security policy, leaving no documented process for reporting and handling vulnerabilities. This weakens transparency, although it does not by itself indicate unsafe code.

Workflow auditcaution

The single workflow was fully analyzed with no untrusted triggers, injection findings, or excessive top-level permissions, but all 3 action references are unpinned. That leaves avoidable build-integrity exposure and warrants a hygiene deduction.