t3docs/blog-example

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement provided. This is a severe adoption risk because future maintenance and support are explicitly uncertain.

Release historydanger

The package has 13 releases since October 2019, but no releases in the last 12 months and its latest release was about 2 years and 4 months ago. The repository's recent commits do not compensate for the lack of current registry releases.

Repository archiveddanger

The linked repository is archived, which is a severe abandonment signal even though it was pushed recently. An archived project should not be treated as an actively maintained dependency.

Repo commit activitycaution

Two commits by two active maintainers were recorded in the last 3 months, showing some current repository activity. This is limited compensation and does not overcome the archived repository or package deprecation.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is an additional transparency gap for a package already carrying strong abandonment signals.