Public package reports pinned to source commits, with Manifest, Patch, license, and freshness evidence kept in view.
Who this is for
A starting point for source review
Plugin maintainers and operators who want to inspect the exact public package snapshot before spending time on a deeper review.
This page gathers approved package reports in one place so readers can compare each report's fixed commit, Manifest and Patch coverage, license state, and freshness. It helps readers find the underlying evidence; it does not decide whether a plugin is safe, compatible, or right for a particular setup.
How reports are selected
Selection method
This page currently links 4 approved package reports. Each entry is selected by its published package ID and links to the fixed-source report that supports its inclusion.
The package has a public, approved fixed-source report.
Its report exposes a stable package ID and source commit SHA.
The page links to the public report instead of duplicating its evidence data.
The list is not a safety ranking or an installation recommendation. Static evidence does not establish runtime behavior, compatibility, or that a package is safe to use.
This approved report records five manifests and a parsed declared Patch at its fixed commit, so readers can inspect how its report covers a multi-manifest package.
This approved report records four manifests and a parsed Patch at its fixed commit. Its update_pending freshness label makes clear this is an older published snapshot, not evidence about a newer revision.
This approved report records its package Manifest and a parsed declared Patch at one fixed commit, with source links that let readers inspect those inputs directly.
This approved report records six manifests and a parsed declared Patch at its fixed commit, providing a concrete example of repository coverage within a package report.