dbpm registry

Oracle package resolution for dbpm. dbpm installs, locks, resolves, and repeats database package deployments. Registry-backed resolution helps dbpm choose compatible signed packages by version, dependency metadata, Core requirements, Oracle compatibility, and publisher trust.

The dbpm registry is metadata-only. Artifact bytes remain in external package storage; dbpm downloads and verifies them.

Database cylinder with an orange package cube

Install and lock

Deploy Oracle database packages through dbpm and keep exact artifact identities in a lockfile for repeatable installs.

Resolve packages

Use registry metadata to find compatible package versions while excluding yanked releases from range queries.

Verify publishers

Production registry metadata is built around detached artifact signatures, publisher keys, and immutable checksums.

Resolve from the registry. Install with dbpm.

The registry answers metadata questions: package version, artifact location, checksum, signature, and compatibility. The dbpm CLI still performs the install and records the exact artifact identity in the lockfile.

repeatable database installs
dbpm install registry:utl_interval@^1.0.0
dbpm lock

{
  "package": "utl_interval",
  "version": "1.2.3",
  "artifact_checksum": "sha256:..."
}