Infoblox Schema Registry - Multi-Architecture Container Image

Portable, multi-architecture OCI container image for Confluent Schema Registry
Built from upstream source without Spotify's dockerfile-maven-plugin

Features

✅ Multi-Architecture: Native support for linux/amd64 and linux/arm64
✅ Secure by Default: Chainguard distroless JRE runtime (~60% smaller, minimal CVEs)
✅ Pluggable Base Images: Swap between Chainguard (default), Eclipse Temurin, or other JRE bases
✅ Supply-Chain Security: Non-root user (UID 65532), OCI labels, reproducible builds, SLSA provenance attestations
✅ Developer Friendly: Simple make build on macOS Apple Silicon or Linux x86
✅ CI/CD Ready: GitHub Actions workflow with multi-arch buildx

Quick Start

Prerequisites

Docker: Version 20.10+ with BuildKit enabled (default in Docker 23.0+)
Docker Buildx: For multi-architecture builds (docker buildx version)
Git: For submodule management
Make: Build automation (pre-installed on macOS/Linux)

Verify Provenance and SBOM (Supply-Chain Security)

All published images from the main branch include SLSA provenance and SBOM attestations that allow you to verify the build origin, integrity, and component inventory:

# Install cosign (one-time setup)
go install github.com/sigstore/cosign/v2/cmd/cosign@latest

# Verify image build provenance
cosign verify-attestation \
  --type slsaprovenance \
  --certificate-identity-regexp '^https://github.com/infobloxopen/ib-schema-registry/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  ghcr.io/infobloxopen/ib-schema-registry:latest

# Verify SBOM attestation (main branch builds only)
cosign verify-attestation \
  --type https://spdx.dev/Document \
  --certificate-identity-regexp '^https://github.com/infobloxopen/ib-schema-registry/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  ghcr.io/infobloxopen/ib-schema-registry:latest

# ✅ Success means: signature valid, built by trusted GitHub Actions workflow

📘 Full verification guides:

Provenance Verification Guide - Verify build provenance attestations
SBOM Attestation Verification Guide - Verify SBOM attestations and scan for vulnerabilities

Build Image

# Clone repository with upstream submodule
git clone --recurse-submodules https://github.com/infobloxopen/ib-schema-registry.git
cd ib-schema-registry

# Build for your native platform (Apple Silicon → ARM64, Linux x86 → AMD64)
make build

# Build for all platforms (AMD64 + ARM64)
make buildx

# Run smoke tests
make test

Run Container

# Start Schema Registry (requires Kafka cluster)
docker run -d \
  --name schema-registry \
  -p 8081:8081 \
  -e SCHEMA_REGISTRY_HOST_NAME=schema-registry \
  -e SCHEMA_REGISTRY_KAFKASTORE_BOOTSTRAP_SERVERS=PLAINTEXT://kafka:9092 \
  -e SCHEMA_REGISTRY_LISTENERS=http://0.0.0.0:8081 \
  ib-schema-registry:latest

# Health check
curl http://localhost:8081/subjects
# Expected: []

Kubernetes Deployment (Helm Chart)

Quick Deploy to Kubernetes

# Install stable release from OCI registry
helm install schema-registry oci://ghcr.io/infobloxopen/ib-schema-registry \
  --version 8.1.1-ib.1.abc1234 \
  --set config.kafkaBootstrapServers="kafka:9092"

# Install development build from main branch
helm install schema-registry-dev oci://ghcr.io/infobloxopen/ib-schema-registry \
  --version 8.1.1-ib.main.abc1234 \
  --set config.kafkaBootstrapServers="kafka:9092"

# Or install from local chart
helm install schema-registry ./helm/ib-schema-registry \
  --set config.kafkaBootstrapServers="kafka:9092"

Helm Chart Versioning

Stable Releases: Charts are automatically published when git tags are pushed:

Git tag v8.1.1-ib.1 → Helm chart version 8.1.1-ib.1.abc1234
Chart version includes full version with commit SHA
AppVersion shows upstream version: 8.1.1
Install: helm install ... oci://ghcr.io/infobloxopen/ib-schema-registry --version 8.1.1-ib.1.abc1234

Development Builds: Charts published for every commit to main branch:

Commit to main → Chart version 8.1.1-ib.main.abc1234
Enables testing pre-release features
Install: helm install ... oci://ghcr.io/infobloxopen/ib-schema-registry --version 8.1.1-ib.main.abc1234

List Available Versions:

# List all published chart versions
helm search repo ib-schema-registry --versions

# Pull specific version
helm pull oci://ghcr.io/infobloxopen/ib-schema-registry --version 8.1.1-ib.1.abc1234

Production HA Deployment

# Deploy with 3 replicas, PodDisruptionBudget, and topology spread
helm install schema-registry oci://ghcr.io/infobloxopen/ib-schema-registry \
  --version 8.1.1-ib.1.abc1234 \
  --set config.kafkaBootstrapServers="kafka-0:9092,kafka-1:9092,kafka-2:9092" \
  --set replicaCount=3 \
  --set resources.requests.memory=1Gi \
  --set resources.limits.memory=2Gi

Helm Chart Features

✅ High Availability: Multi-replica with PodDisruptionBudget and zone distribution
✅ Rolling Updates: Automatic pod restarts on configuration changes
✅ Security: Non-root, read-only filesystem, minimal privileges
✅ E2E Tested: Validated with k3d and Redpanda in CI/CD

See helm/ib-schema-registry/README.md for full Helm chart documentation.

Monitoring

Prometheus Metrics

The container image includes optional Prometheus JMX metrics export for monitoring Schema Registry health and performance.

Enable Metrics with Helm

helm install schema-registry oci://ghcr.io/infobloxopen/ib-schema-registry \
  --version 8.1.1-ib.1.abc1234 \
  --set config.kafkaBootstrapServers="kafka:9092" \
  --set metrics.enabled=true

When enabled:

HTTP /metrics endpoint exposed on port 9404
Prometheus scrape annotations added to pods
Exports Schema Registry JMX MBeans + JVM metrics

Access Metrics

# Port-forward metrics port
kubectl port-forward svc/schema-registry 9404:9404

# Query metrics endpoint
curl http://localhost:9404/metrics

# Sample metrics:
# kafka_schema_registry_jetty_requests_total 12345.0
# kafka_schema_registry_jersey_request_count{path="/subjects"} 5678.0
# kafka_schema_registry_master_slave_role 1.0
# jvm_memory_heapmemoryusage_used 2.68435456E8

Exported Metrics

Schema Registry Metrics: HTTP requests, API endpoint metrics, master/slave role
JVM Metrics: Memory usage, garbage collection, threads, CPU

Custom Configuration

Customize which metrics are exported:

helm install schema-registry oci://ghcr.io/infobloxopen/ib-schema-registry \
  --set metrics.enabled=true \
  --set metrics.port=9999 \
  --set-file metrics.config=./custom-jmx-config.yaml

📘 Full monitoring guide: helm/ib-schema-registry/README.md#monitoring

Versioning

Version Format

All artifacts (Docker images, Helm charts) use a unified versioning scheme:

<upstream>-ib.<suffix>.<sha>[.dirty]

Examples:

Release: 8.1.1-ib.1.abc1234 (from git tag v8.1.1-ib.1)
Main branch: 8.1.1-ib.main.abc1234 (development builds)
Feature branch: 8.1.1-ib.feature-auth.abc1234 (PR validation)

Components

Component	Description	Example
`8.1.1`	Upstream Confluent Schema Registry version	`8.1.1`
`-ib.`	Infoblox identifier (constant)	`-ib.`
`1` or `main`	Release number OR branch name	`1`, `main`, `feature-auth`
`.abc1234`	Git commit SHA (7 chars)	`.abc1234`
`.dirty`	Optional: uncommitted changes	`.dirty`

Check Your Version

# Display version information
make version

# Example output:
# VERSION = 8.1.1-ib.main.abc1234
# UPSTREAM_VERSION = 8.1.1
# SHA = abc1234
# DIRTY = false

# Validate version format
make version-validate

Why This Format?

OCI Registry Compatibility: The previous format (7.6.1+infoblox.1) used + (build metadata), which is not supported by OCI registries like GHCR. The new format uses - (prerelease identifiers) for universal compatibility.

Traceability: Every version includes the commit SHA, enabling:

Source code lookup: https://github.com/infobloxopen/ib-schema-registry/commit/abc1234
Reproducible builds from exact commit
Supply chain verification with SLSA provenance

For complete versioning documentation, see docs/versioning.md.

Docker Compose Example

version: '3.8'

services:
  schema-registry:
    image: ib-schema-registry:latest
    ports:
      - "8081:8081"
    volumes:
      # Optional: Mount custom configuration
      - ./custom-config.properties:/etc/schema-registry/schema-registry.properties:ro
    depends_on:
      - kafka
    restart: unless-stopped

  # Kafka cluster services (zookeeper, kafka) not shown

Configuration

Default Configuration

The image includes sensible defaults for local development:

listeners=http://0.0.0.0:8081
kafkastore.bootstrap.servers=PLAINTEXT://kafka:9092
schema.registry.group.id=schema-registry
kafkastore.topic=_schemas
kafkastore.topic.replication.factor=1
schema.compatibility.level=BACKWARD

Custom Configuration

For production deployments, you'll want to customize the Schema Registry configuration to match your Kafka cluster and security requirements.

Example Configuration Templates:

The repository provides example configurations in config/examples/:

production.properties: Production-ready template with SSL, SASL, monitoring, and best practices
development.properties: Minimal local development setup with permissive settings

Option 1: Mount Configuration File (Recommended)

The cleanest approach is to mount your custom configuration file into the container:

# Use production example as template
cp config/examples/production.properties my-config.properties
# Edit my-config.properties with your Kafka bootstrap servers, SSL certs, etc.

docker run -d \
  -v $(pwd)/my-config.properties:/etc/schema-registry/schema-registry.properties:ro \
  -p 8081:8081 \
  ib-schema-registry:latest

Docker Compose with Custom Config:

version: '3.8'

services:
  schema-registry:
    image: ib-schema-registry:latest
    ports:
      - "8081:8081"
    volumes:
      - ./config/production.properties:/etc/schema-registry/schema-registry.properties:ro
      # Mount SSL certificates if using secure Kafka
      - ./certs/kafka.truststore.jks:/etc/schema-registry/kafka.truststore.jks:ro
      - ./certs/kafka.keystore.jks:/etc/schema-registry/kafka.keystore.jks:ro
    environment:
      # Pass secrets as environment variables (reference them in properties file)
      - TRUSTSTORE_PASSWORD=${TRUSTSTORE_PASSWORD}
      - KEYSTORE_PASSWORD=${KEYSTORE_PASSWORD}
      - KEY_PASSWORD=${KEY_PASSWORD}
    depends_on:
      - kafka
    restart: unless-stopped

Option 2: Environment Variables

Schema Registry supports environment variable overrides using SCHEMA_REGISTRY_ prefix. Convert property names:

Replace . with _
Convert to uppercase
Add SCHEMA_REGISTRY_ prefix

Examples:

# listeners=http://0.0.0.0:8081
# becomes:
-e SCHEMA_REGISTRY_LISTENERS=http://0.0.0.0:8081

# kafkastore.bootstrap.servers=PLAINTEXT://kafka:9092
# becomes:
-e SCHEMA_REGISTRY_KAFKASTORE_BOOTSTRAP_SERVERS=PLAINTEXT://kafka:9092

# schema.compatibility=BACKWARD
# becomes:
-e SCHEMA_REGISTRY_SCHEMA_COMPATIBILITY=BACKWARD

Full example with environment variables:

docker run -d \
  -v /path/to/production.properties:/etc/schema-registry/schema-registry.properties:ro \
  -p 8081:8081 \
**Full example with environment variables**:

```bash
docker run -d \
  -e SCHEMA_REGISTRY_LISTENERS=http://0.0.0.0:8081 \
  -e SCHEMA_REGISTRY_KAFKASTORE_BOOTSTRAP_SERVERS=PLAINTEXT://prod-kafka-1:9092,PLAINTEXT://prod-kafka-2:9092 \
  -e SCHEMA_REGISTRY_SCHEMA_REGISTRY_GROUP_ID=schema-registry-prod \
  -e SCHEMA_REGISTRY_SCHEMA_COMPATIBILITY=BACKWARD \
  -p 8081:8081 \
  ib-schema-registry:latest

Configuration Precedence:

Environment variables (SCHEMA_REGISTRY_*) - highest priority
Mounted configuration file (/etc/schema-registry/schema-registry.properties)
Built-in defaults - lowest priority

Important Configuration Properties:

Property	Description	Example
`kafkastore.bootstrap.servers`	Kafka cluster connection (REQUIRED)	`PLAINTEXT://kafka:9092`
`listeners`	Schema Registry HTTP endpoint	`http://0.0.0.0:8081`
`schema.registry.group.id`	Unique cluster identifier	`schema-registry-prod`
`kafkastore.topic`	Internal storage topic	`_schemas` (default)
`schema.compatibility`	Default compatibility mode	`BACKWARD`, `FORWARD`, `FULL`
`kafkastore.security.protocol`	Kafka encryption/auth	`PLAINTEXT`, `SSL`, `SASL_SSL`

See Confluent documentation for full configuration reference.

Advanced Usage

Alternative Base Images

Default: Chainguard JRE (distroless, minimal CVEs)

To use Eclipse Temurin instead:

# Build with Temurin JRE (larger image, more tooling)
make build RUNTIME_IMAGE=eclipse-temurin:17-jre

# Note: Chainguard is ~60% smaller with significantly fewer CVEs

Pin Base Images by Digest

For production, pin base images by digest for reproducibility:

make build \
  BUILDER_IMAGE=maven@sha256:abc123... \
  RUNTIME_IMAGE=cgr.dev/chainguard/jre@sha256:def456...

Custom Image Tags

# Build with custom name and version
make build IMAGE=ghcr.io/infobloxopen/schema-registry TAG=v8.1.1

# Push to registry
make push IMAGE=ghcr.io/infobloxopen/schema-registry TAG=v8.1.1

Update Upstream Version

# Update to latest Schema Registry release
make submodule-update

# Or manually
cd upstream/schema-registry
git fetch --tags
git checkout v7.7.0
cd ../..

# Rebuild image
make build

Makefile Targets

Target	Description
`help`	Display available targets (default)
`submodule-init`	Initialize upstream Schema Registry submodule
`submodule-update`	Update upstream to latest version
`build`	Build image for native platform
`buildx`	Build multi-arch image (AMD64 + ARM64)
`push`	Push multi-arch image to registry
`test`	Run smoke tests
`clean`	Remove local images
`info`	Display build configuration

CI/CD Integration

GitHub Actions

The repository includes a multi-arch CI workflow:

# .github/workflows/build-image.yml
# Triggers: Push to main, pull requests
# Platforms: linux/amd64, linux/arm64
# Registry: GitHub Container Registry (ghcr.io)

On PR: Build and validate (no registry push)
On main: Build, tag with commit SHA + latest, and push to GHCR
On tag: Build, tag with version number, and push to GHCR

Build Times

Scenario	Expected Time
Cold build (no cache)	~15 minutes
Warm build (Maven cache hit)	~5 minutes
Multi-arch buildx	~15 minutes (parallel)

Architecture

┌─────────────────────────────────────────────────────┐
│  Multi-Stage Dockerfile                              │
├─────────────────────────────────────────────────────┤
│  Builder Stage (BUILDPLATFORM)                       │
│  ├─ Base: Maven 3 + Eclipse Temurin 17 JDK          │
│  ├─ Copy: upstream/schema-registry (submodule)      │
│  ├─ Build: mvn -DskipTests package -P standalone    │
│  └─ Output: kafka-schema-registry-*-standalone.jar  │
├─────────────────────────────────────────────────────┤
│  Runtime Stage (TARGETPLATFORM)                      │
│  ├─ Base: Chainguard JRE (distroless, minimal CVEs) │
│  ├─ User: 65532 (nobody, non-root)                  │
│  ├─ Copy: Standalone JAR + config                   │
│  ├─ Expose: Port 8081                               │
│  └─ Entrypoint: java -jar (JSON exec-form)          │
└─────────────────────────────────────────────────────┘

Troubleshooting

Build Errors

Error: submodule not initialized

make submodule-init

Error: BUILDPLATFORM is blank

# Enable BuildKit
export DOCKER_BUILDKIT=1

Error: Maven build failed

# Check submodule is on valid tag
cd upstream/schema-registry
git describe --tags
cd ../..

# Clean and retry
make clean && make build

Runtime Errors

Container exits immediately

# Check logs
docker logs <container-name>

# Verify Kafka is reachable
docker exec <container-name> ping kafka

Health check fails

# Verify port mapping
docker ps | grep schema-registry

# Test locally
curl http://localhost:8081/subjects

Platform Issues

ARM vs x86 dependency resolution

Builder stage runs on BUILDPLATFORM (native architecture) for speed
Maven resolves dependencies for native platform, avoiding cross-compilation
Runtime stage uses TARGETPLATFORM (target architecture)

Compliance & Licensing

⚠️ Confluent Community License

This repository contains build tooling only (MIT licensed). The actual Confluent Schema Registry source code is subject to the Confluent Community License.

Key Restrictions:

❌ Providing Schema Registry as a hosted/managed service to third parties is prohibited
✅ Using Schema Registry for internal infrastructure is allowed
✅ Modifying build tooling in this repository is allowed

Full License Text: See LICENSE.md for details and compliance guidance.

Disclaimer: This is not legal advice. Consult your legal counsel for commercial use.

Contributing

See CONTRIBUTING.md for development workflow, testing guidelines, and PR process.

SBOM (Software Bill of Materials)

This project generates comprehensive SBOMs for all container images built from the main branch, with cryptographic attestations binding each SBOM to the exact container image digest.

Features

✅ Dual Format Support: CycloneDX 1.5 and SPDX 2.3
✅ Multi-Architecture: Separate SBOMs for AMD64 and ARM64
✅ Automated Generation: Integrated into main build workflow
✅ Cryptographically Bound: SBOM attestations linked to image digest
✅ Vulnerability Scanning: Compatible with Grype, Trivy, and Snyk
✅ 90-Day Retention: SBOMs stored as GitHub Actions artifacts
✅ Supply Chain Security: Generated only from trusted main branch builds

Quick Start - Verify and Extract SBOM

# Install cosign (one-time setup)
go install github.com/sigstore/cosign/v2/cmd/cosign@latest

# Verify SBOM attestation and extract SBOM
cosign verify-attestation \
  --type https://spdx.dev/Document \
  --certificate-identity-regexp '^https://github.com/infobloxopen/ib-schema-registry/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  ghcr.io/infobloxopen/ib-schema-registry:latest \
  | jq -r '.payload | @base64d | fromjson | .predicate' > sbom.spdx.json

# Scan for vulnerabilities
grype sbom:./sbom.spdx.json

Local SBOM Generation

For local development and testing:

# Build image
make build

# Generate SBOM (both formats)
make sbom

# Validate and scan for vulnerabilities
make sbom-validate

# Scan with Grype
grype sbom:build/sbom/latest-amd64.cyclonedx.json

Multi-Architecture SBOMs

Generate SBOMs for all platforms locally:

# Build multi-arch image
make buildx

# Generate SBOMs for both amd64 and arm64
make sbom-multi

CI/CD Integration

SBOMs are automatically generated in GitHub Actions only for main branch builds:

Trigger: Pushes to main branch (not PRs or feature branches)
Platforms: linux/amd64, linux/arm64
Formats: CycloneDX JSON and SPDX JSON
Attestations: Cryptographically signed and bound to image digest
Artifacts: Available for download (90-day retention)

Download SBOMs from GitHub Actions:

# Using GitHub CLI
gh run list --repo infobloxopen/ib-schema-registry --branch main --limit 1
gh run download <run-id> -n sbom-artifacts

# Files downloaded:
# - sbom-amd64.cyclonedx.json (vulnerability scanning)
# - sbom-amd64.spdx.json (attestation format)
# - sbom-arm64.cyclonedx.json (vulnerability scanning)
# - sbom-arm64.spdx.json (attestation format)

SBOM Attestation Verification

Full verification workflow combining build provenance and SBOM:

IMAGE="ghcr.io/infobloxopen/ib-schema-registry:latest"

# 1. Verify build provenance
echo "Verifying build provenance..."
cosign verify-attestation \
  --type slsaprovenance \
  --certificate-identity-regexp '^https://github.com/infobloxopen/ib-schema-registry/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  "$IMAGE"

# 2. Verify SBOM attestation
echo "Verifying SBOM attestation..."
cosign verify-attestation \
  --type https://spdx.dev/Document \
  --certificate-identity-regexp '^https://github.com/infobloxopen/ib-schema-registry/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  "$IMAGE"

# 3. Extract and analyze SBOM
echo "Extracting SBOM..."
cosign verify-attestation \
  --type https://spdx.dev/Document \
  --certificate-identity-regexp '^https://github.com/infobloxopen/ib-schema-registry/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  "$IMAGE" \
  | jq -r '.payload | @base64d | fromjson | .predicate' > sbom.spdx.json

echo "✅ Complete supply chain verification successful"

📘 Full SBOM documentation: See docs/sbom-attestation-verification.md for comprehensive verification, vulnerability scanning, and compliance guidance.

Available Make Targets

Target	Description
`sbom-install-tools`	Install Syft and Grype tools
`sbom`	Generate SBOM for native platform (both formats)
`sbom-multi`	Generate SBOMs for all architectures
`sbom-validate`	Validate SBOMs and scan for vulnerabilities
`sbom-clean`	Remove generated SBOM files

SBOM Standards

CycloneDX 1.5: Recommended for vulnerability scanning (cyclonedx.org)
SPDX 2.3: ISO standard for license compliance (spdx.dev)

Tools Used

Syft (Anchore): SBOM generation (github.com/anchore/syft)
Grype (Anchore): Vulnerability scanning (github.com/anchore/grype)

For detailed documentation, see build/sbom/README.md.

Support

Issues: GitHub Issues
Upstream Docs: Confluent Schema Registry Docs
Specification: specs/001-schema-registry-image/

Roadmap

Helm chart for Kubernetes deployments
SBOM generation (Software Bill of Materials)
Provenance attestation (SLSA framework) - [Implemented]
Image signing with cosign
Performance benchmarking suite

License

Build Tooling (this repository): MIT License
Confluent Schema Registry (upstream): Confluent Community License

See LICENSE.md for full details.

Built with ❤️ by Infoblox | Constitution | Specification

Name		Name	Last commit message	Last commit date
Latest commit History 33 Commits
.github		.github
.specify		.specify
build/sbom		build/sbom
config		config
docs		docs
helm/ib-schema-registry		helm/ib-schema-registry
patches		patches
scripts		scripts
specs		specs
tests		tests
upstream		upstream
.dockerignore		.dockerignore
.gitignore		.gitignore
.gitmodules		.gitmodules
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile		Dockerfile
LICENSE.md		LICENSE.md
Makefile		Makefile
README.md		README.md
constitution-validation.md		constitution-validation.md

License

infobloxopen/ib-schema-registry

Folders and files

Latest commit

History

Repository files navigation

Infoblox Schema Registry - Multi-Architecture Container Image

Features

Quick Start

Prerequisites

Verify Provenance and SBOM (Supply-Chain Security)

Build Image

Run Container

Kubernetes Deployment (Helm Chart)

Quick Deploy to Kubernetes

Helm Chart Versioning

Production HA Deployment

Helm Chart Features

Monitoring

Prometheus Metrics

Enable Metrics with Helm

Access Metrics

Exported Metrics

Custom Configuration

Versioning

Version Format

Components

Check Your Version

Why This Format?

Docker Compose Example

Configuration

Default Configuration

Custom Configuration

Advanced Usage

Alternative Base Images

Pin Base Images by Digest

Custom Image Tags

Update Upstream Version

Makefile Targets

CI/CD Integration

GitHub Actions

Build Times

Architecture

Troubleshooting

Build Errors

Runtime Errors

Platform Issues

Compliance & Licensing

⚠️ Confluent Community License

Contributing

SBOM (Software Bill of Materials)

Features

Quick Start - Verify and Extract SBOM

Local SBOM Generation

Multi-Architecture SBOMs

CI/CD Integration

SBOM Attestation Verification

Available Make Targets

SBOM Standards

Tools Used

Support

Roadmap

License

About

Resources

License

Contributing

Uh oh!

Stars

Watchers

Forks

Releases 1

Packages 0

Uh oh!

Uh oh!

Contributors 2

Uh oh!

Languages

Packages