camelcase-css

Release historydanger

The package has had no release in about 8 years, with 0 releases in the last 12 months. Its four-release history shows limited ongoing maintenance despite its long age.

Build provenancecaution

No build attestation or trusted-publisher provenance is available, so consumers cannot verify how the registry artifact was produced. This is a supply-chain transparency gap, not evidence of maliciousness.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers in the last 3 months. A push in March 2023 shows it is not archived, but current development activity is absent.

Repo toolingcaution

The repository uses Babel, but no security-scanning tools are reported. For a small dependency-free utility this is a modest transparency gap rather than a severe risk.

Security policycaution

No repository security policy is present. This weakens vulnerability-reporting transparency, though the package's small scope and lack of runtime dependencies reduce the practical impact.