Open Policy Registry (OPCR)
/All repositories
Overview
HEALTH SCORE
Critical
7out of 100
Security posture is the primary crisis signal. Maintainer coverage and development cadence show little to offset it. Every health signal is at or near zero.
LIFECYCLE
Active
Consistent commits, responsive maintainers, regular releases, and healthy issue triage.
Health breakdown
Critical(7/100)
Maintainer availability, known risks and supply chain posture, and whether the project is actively developed or appropriately stable.
Maintainer responsiveness
Median response time is 4 days, but most repositories have response times over 90 days.
Bus factor
Only 1 active maintainer currently has merge rights.
Organization Diversity
Contributors come from 15 organizations only.
Project Achievements
Leaderboards
About
The Open Policy Registry (OPCR) project contains a CLI (policy) for building, tagging, pushing, and pulling OPA policies as OCIv2 images. The policy CLI defaults to pushing and pulling from opcr.io, a free hosted registry that is optimized around listing and handling policy images. With that said, the policy CLI works with any OCIv2-compatible registry, such as GitHub Container Registry, Google Artifact Registry, AWS Container Registry, etc.
The ecosystem benefits of using the policy CLI are that policies can now be built into immutable images, signed using cosign, and pushed and pulled from container registries - in other words, the benefits of the OCIv2 ecosystem are now conferred to OPA policies.
The policy CLI workflow is modeled after the docker CLI - with the ability to build images locally (""policy build""), tag them (""policy tag""), list them (""policy images""), pull them (""policy pull""), and push them (""policy push""). This brings the familiar workflow to the OPA policies.
First commit
Software value
$352K
Maturity
Sandbox
License(s)
Apache-2.0
Data sources
Stack Overflow
Git
GitHub
Hacker News