christianessl/yaml_browser

Release historydanger

This is the package's only release, published about seven years ago, with no releases in the last 12 months; that is strong evidence of limited ongoing maintenance.

Repo commit activitydanger

The repository has recorded zero commits and zero active maintainers in the last three months, while its last push was nearly five years ago; no provided evidence compensates for the age.

Repo issue activitycaution

There are four open issues and one open pull request, but no new or closed issues or pull requests in the last month, suggesting unresolved maintenance demand.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present; this is a modest transparency and maintenance-hygiene gap rather than evidence of abandonment.

Security policycaution

The repository has no security policy, which leaves vulnerability reporting and maintenance expectations undocumented.