alibabacloud/jarvis

Release historydanger

The latest release was about 5 years ago, with no releases in the last 12 months, despite a previously rapid release cadence. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months. Combined with the old latest release, this confirms that maintenance has effectively stopped.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. This is a hygiene concern, though it is secondary to the much larger maintenance gap.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This lowers transparency but is less serious than the long inactivity period.