stuk/jszip

Release historydanger

The package has had no releases in about 10 years, with only three releases overall. This is strong evidence of abandonment risk despite the package having a documented history.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the measured three-month period, reinforcing the long release gap and indicating no recent maintenance.

Repo popularitycaution

The linked repository has 0 stars, 1 fork, and 1 watcher, providing little supporting evidence of an active user or contributor community.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That is a maintenance and assurance gap, though it is less serious than the lack of recent activity.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This adds transparency risk to an otherwise well-documented package.