Skip to content

Releases: paramify/paramify-fetchers

v0.2.1-beta

v0.2.1-beta Pre-release
Pre-release

Choose a tag to compare

@21tmccauley 21tmccauley released this 10 Jul 16:52
f4071aa

What's Changed

  • chore(deploy): trim to a Docker-only bundle for public release by @21tmccauley in #11

Full Changelog: v0.2.0-beta...v0.2.1-beta

v0.2.0-beta

v0.2.0-beta Pre-release
Pre-release

Choose a tag to compare

@21tmccauley 21tmccauley released this 10 Jul 16:08
ac8e1f7

v0.2.0-beta — first public (beta) release

Paramify Fetchers collects compliance evidence from the tools you already run and writes it to disk as JSON; a separate uploader pushes that evidence to Paramify. Everything runs on your infrastructure — the fetchers never talk to Paramify directly. This is the first public cut: usable and tested end-to-end, but pre-1.0, so expect some rough edges and a contract that may still shift before 1.0.
Feedback and bug reports are very welcome.

Highlights

  • 100+ evidence fetchers across 8 categories — AWS (79), Okta, SentinelOne, KnowBe4, GitLab, Kubernetes, Rippling, and Checkov IaC scans.
  • Three ways to drive it — an interactive TUI, a machine-readable --json surface for AI agents and scripts, and the CLI directly. All go through one facade, so they behave identically.
  • Self-describing, schema-validated contract — every fetcher declares what it needs in fetcher.yaml; the runner treats them all uniformly.
  • Evidence envelope — every output is wrapped in {schema_version, metadata, payload} (envelope schema_version 1.0).
  • Upload stageparamify upload pushes a run's evidence to Paramify.
  • Contract-gated CI + documented versioning — see docs/versioning.md.

Install

git clone https://github.com/paramify/paramify-fetchers.git
cd paramify-fetchers
python -m venv .venv && source .venv/bin/activate
pip install -e '.[all]'      # '[all]' includes the TUI
paramify tui                 # or: paramify run examples/demo.yaml  (no credentials)

Requires Python 3.10+.

This is a beta — what that means

  • Pre-1.0. The contract (fetcher / manifest / envelope schemas + the paramify CLI) may still change; breaking changes bump the minor version
  • Review category-specific config before trusting the evidence — some fetchers still carry environment-specific defaults (e.g. KnowBe4 training- campaign names) that you may need to adjust for your tenant.

Docs

Quickstart & usage → README · Contract → docs/fetcher_contract.md · Manifest
format → docs/run_manifest_reference.md · Releasing → docs/releasing.md.

Licensed under GPL-3.0-only.