izzle/csv

Release historydanger

Only three releases were published, with the latest in February 2018 and none in roughly eight years. This is strong evidence of abandonment for a library dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the multi-year release gap and increasing abandonment risk.

Project backingcaution

The repository is owned by the iz​​zle-org organization, which provides some ownership context, but the activity signals do not show an active backing team.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these counts provide no supporting evidence of adoption or community resilience.

Repo toolingcaution

Composer is used for builds, but no security scanning tooling is present. The missing scanning is a modest transparency and maintenance weakness rather than a standalone severe risk.