parsidev/jalali

Release historydanger

Only two releases exist, with the latest published in September 2020 and none in the last 12 months. That makes this release substantially stale for a Laravel dependency, despite the linked repository remaining available.

Project backingcaution

The registry namespace and repository are owned by the same individual account, so there is no organizational backing shown to compensate for the thin maintainer base.

Repo commit activitycaution

There were no commits and no active maintainers in the three months measured. Combined with the old registry release, this weakens confidence in ongoing maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a small package this is a modest transparency and hygiene gap, not evidence of abandonment by itself.

Security policycaution

The repository has no security policy. This reduces transparency about vulnerability reporting and handling, though it is a secondary concern for this small package.