pascal-case

Registry deprecationdanger

The entire package is deprecated on npm, with users directed to change-case. Package-level deprecation is a decisive adoption risk even though the linked project remains active.

Release historycaution

The package has had no registry release in nearly three years, despite an otherwise mature history of 16 releases. This increases abandonment and stale-dependency risk.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last three months. This is concerning for ongoing maintenance, although the recent push and package deprecation indicate the project may have shifted users elsewhere.

Repo package mentioncaution

The linked repository neither matches the package name nor mentions pascal-case in its README. Although this appears consistent with a broader change-case repository, the package-to-repository relationship is less transparent.

Workflow auditcaution

The single workflow was fully audited with no reported findings or dangerous triggers, but all three action references are unpinned. That is a modest reproducibility and supply-chain hygiene gap, not a severe risk on its own.