violinist-dev/composer-lock-data

Release historydanger

Only two releases were published, with the latest more than seven years ago and none in the past 12 months. This is strong evidence of abandonment risk despite the package being stable.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the past three months, reinforcing the more than seven-year release gap and increasing abandonment risk.

Repo issue activitycaution

There are no open issues or pull requests and no issue or pull-request activity in the past month. This is consistent with an inactive project, though the package may simply be small and stable.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. The absence of scanning is a modest transparency gap rather than a severe dependency risk.

Security policycaution

No security policy was found in the repository, leaving vulnerability reporting and response expectations undocumented.