chevron/kernel

Release historydanger

The last release was in August 2016, and there have been no releases in roughly 10 years despite 23 historical releases. This is strong evidence of abandonment for a package intended as an application framework component.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The non-archived status does not compensate for the absence of observed development.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month. This supports the broader inactivity concern, although an empty issue queue is less conclusive than the lack of commits and releases.

Security policycaution

No security policy was found in the linked repository, so there is no documented process for reporting vulnerabilities. This is a transparency gap, though it is less significant than the maintenance evidence.

Version stabilitycaution

The latest release is still v0.14.0 rather than a stable major version, and the README explicitly describes the project as unstable. That makes API and maintenance risk higher for adopters.