reactcss

Release historydanger

The package has 26 releases, but none in the last 12 months and the latest release was in September 2017, roughly 9 years ago. This is strong evidence of abandonment risk despite an earlier regular cadence.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months, consistent with the long release gap. The repository is not archived, but that does not offset the absence of recent development.

Build provenancecaution

No build attestation or trusted-publisher provenance is available, so consumers cannot verify how the registry artifact was produced. This lowers supply-chain transparency but is not by itself evidence that the package is unsafe.

Maintainerscaution

Only one account has registry publish access. Because this is a user-owned project rather than organization-backed publishing, the narrow publishing base adds some continuity risk, though registry access alone does not prove inactivity.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while 2 issues and 5 pull requests remain open. This suggests limited current maintenance attention.