Skip to main content

datafog

datafog core

Find and transform sensitive data in your application.

PyPI version npm version crates.io version Rust CI status MIT license

Quickstart · Detection · Transformations · Local models · Documentation

datafog core is a Rust library with Python, Node.js, and browser WebAssembly bindings. Scan text or JSON for personal data and credentials, then redact, mask, remove, pseudonymize, or tokenize matched values. Findings use a consistent format across the bindings.

Rule-based scanning runs locally without model weights or downloads. Optional local model sessions add datafog and GLiNER2 support in Rust, Python, and Node.js.

Release: coordinated Core 1.6.0 for Python, Rust, Node.js, WASM and the Core-owned companion packages · 1.6 release notes · Python release history · 1.5 migration guide · Earlier cross-SDK 1.1.0 notes · Extension installation and testing.

Core 1.0 freezes Workspace contract 1 across Rust, Python, Node and browser WASM, with optional native/browser FogVault integrations. Snapshot v3 writes and v1/v2/v3 reads keep their existing semantics. Exact published 0.5.0-beta.3 interchange remains tested; FogVault is independently versioned 0.1.0.

Quickstart

The coordinated Core release is 1.6.0 across PyPI, crates.io and npm. Applications should lock the exact version they have qualified. The datafog Python application and FogVault version independently of Core.

SDK Published install Requirements
Python python -m pip install datafog-core==1.6.0 Python 3.10+
Node.js npm install --save-exact @datafog/node@1.6.0 Node.js 24+
Rust cargo add datafog-core@=1.6.0 Rust 1.88+
Browser / WASM npm install --save-exact @datafog/wasm@1.6.0 Browser with WebAssembly support

Python

from datafog_core import scan, scan_and_transform

findings = scan("Email jane@example.com")
print(findings[0].entity_type)   # EMAIL
print(findings[0].matched_text)  # jane@example.com

result = scan_and_transform(
    "Email jane@example.com",
    {"transform": {"default": {"strategy": "redact"}}},
)
print(result.text)  # Email [EMAIL]
Node.js example
import { scan, scanAndTransform } from "@datafog/node";

const findings = scan("Email jane@example.com");
console.log(findings[0].entityType); // EMAIL
console.log(findings[0].matchedText); // jane@example.com

const result = scanAndTransform("Email jane@example.com", {
  transform: { default: { strategy: "redact" } },
});
console.log(result.text); // Email [EMAIL]
Rust example
use datafog_core::{
    scan, scan_and_transform, PrivacyError, ScanAndTransformConfig,
    TransformationConfig, TransformationStrategy,
};

fn main() -> Result<(), PrivacyError> {
    let findings = scan("Email jane@example.com");
    println!("{}", findings[0].entity_type); // EMAIL
    println!("{}", findings[0].matched_text); // jane@example.com

    let result = scan_and_transform(
        "Email jane@example.com",
        &ScanAndTransformConfig::new(TransformationConfig::new(
            TransformationStrategy::Redact,
        )),
    )?;
    println!("{}", result.text); // Email [EMAIL]
    Ok(())
}
Browser / WASM example
import { init, scan, scanAndTransform } from "@datafog/wasm";

await init();
console.log(scan("Email jane@example.com"));

const result = scanAndTransform("Email jane@example.com", {
  transform: { default: { strategy: "redact" } },
});
console.log(result.text); // Email [EMAIL]

The Python package ships CPython 3.10+ ABI3 wheels for Linux x64 and ARM64 (manylinux_2_28 and musllinux_1_2), Linux s390x and ppc64le (manylinux_2_28), macOS Intel 10.12+ and Apple Silicon 11+, and Windows x64/ARM64. The Node.js 1.6.0 package ships Linux x64/ARM64 GNU, macOS Intel/Apple Silicon, and Windows x64 binaries.

PyPy, free-threaded CPython, older glibc/musl and other architectures fall back to a source build. That route requires Rust 1.88+, Cargo, a native linker and access to the Rust build dependencies; installation can take several minutes. To require a prebuilt wheel, use python -m pip install --only-binary=:all: datafog-core. See installation requirements.

Detection coverage

Coverage Entity types Activation
Personal and financial data EMAIL, PHONE, SSN, CREDIT_CARD, IP_ADDRESS, DATE, ZIP_CODE On by default
Credentials API_KEY, BEARER_TOKEN, JWT, PRIVATE_KEY, CREDENTIAL_URI On by default
Labeled street addresses STREET_ADDRESS On by default; bounded English street-line rule
Labeled accounts ACCOUNT_NUMBER On by default; bounded lexical rule
Labeled US identifiers US_ROUTING_NUMBER, NPI On by default; requires a supported text label
German identifiers IBAN, VAT ID, tax ID, social security number, postal code, passport number, residence permit number Explicit German locale
UUIDs UUID Explicit detect_uuid setting
Names in JSON fields PERSON Structured scans, using name-field aliases or explicit JSON Pointer mappings
Names and address blocks in prose PERSON, ADDRESS EmbeddedCnnDetector: weights compiled into the extension, no download or runtime
Caller-defined labels any GLiNER2 model sessions

Use structured scans to find names by JSON field, EmbeddedCnnDetector for recipient names and mailing-address blocks in prose, or model sessions for caller-defined labels.

Each finding includes its entity type, matched text, byte and code-point ranges, optional confidence, and detector name/version. Ranges are zero-based and end-exclusive. Node.js and WASM also provide UTF-16 ranges for JavaScript slice. Rule-based findings have no confidence score. Findings and ranges →

For scanning files from AI agents, use datafog MCP.

Detection settings
  • Select checks: scan(text, {"entities": ["EMAIL", "SSN"]}) in Python runs only the selected text detectors. Omit entities to use all enabled detectors. Selections must be nonempty, unique, exact entity names. Selecting a German type or UUID does not activate it; set locale or detect_uuid too.
  • Literal denylists: {"deny": [{"phrase": "Project Atlas"}]} adds explicit sensitive phrases. Rules default to case-sensitive whole-phrase word boundaries; substring and Unicode case-insensitive options are available. Explicit deny matches win allowlists. Matching and policy rules →
  • German locale: {"locale": "de"} enables the seven German detectors. These use format/context rules; IBAN checksums and account existence are not verified. See the German reference for detector rules.
  • ENV and SQL: choose format: "env" or format: "sql" to handle email boundaries in assignments and quoted strings. Source-context rules →
  • Phone numbers: numbers without + use North American checks: ten digits, optionally preceded by 1, with area codes starting with 2–9 and exchange codes starting with 1–9. Numbers starting with + use a permissive 7–15 digit check, including shortened examples such as +1-555-1002. Country codes and assigned numbers are not validated; numeric identifiers can still match.
  • Decimal numbers and CSV: contiguous card digits after a digit and . or , are suppressed, so 3.4111111111111111 and 3,4111111111111111 do not produce card findings. Cards containing spaces or hyphens still undergo normal checks. Parse CSV/TSV into cells before scanning so delimiters and adjacent fields do not affect matching.

Use capabilities() in Rust or Python to discover supported entities and their activation rules.

Transformations

Strategy Result Application provider Browser / WASM
redact Replace with a label such as [EMAIL] None Supported
mask Replace characters, optionally revealing the first or last characters None Supported
remove Delete the matched span None Supported
pseudonymize Create a stable keyed HMAC-SHA-256 pseudonym Key provider Unsupported
tokenize Issue an opaque token that can be restored under the same scope Token provider Unsupported

Use transform with existing findings, or scan_and_transform / scanAndTransform to scan and transform together. Transformation records include source/output ranges and replacement metadata, without the original matched text.

Keep scan settings under scan and transformation policy under transform. A default strategy is required; entity selection, per-type overrides, and allowlists are optional. Configuration guide → · Strategy details →

Browser workspace and FogVault integration

The unreleased v1.1 browser extension flow adds a bundled, default-enabled name/address CNN with a disable control, plus SQLite3 Multiple Ciphers as a second encrypted Workspace backend. See the candidate integration guide.

Core 1.0 provides persistent Workspace pseudonyms, explicit approved saves, strict/progressive restoration, operation history and conversation-scoped recall. The optional browser adapter uses the maintained FogVault Worker/WASM owner and IndexedDB storage. Native Rust, Node and Python owners use the same portable vault core through the registered native adapter.

Install the browser integration:

npm install --save-exact @datafog/wasm@1.6.0 @datafog/fogvault-browser@0.1.0 @datafog/core-fogvault-browser@1.6.0

Integration guide and supported profiles → · Stable Workspace contract → · Model assets and runtime setup → · SDK release scope and separate extension acceptance →

Local models (beta)

Core 1.0 includes optional local sessions for the datafog PII model and GLiNER2 in Rust, Python and Node.js. Model files are provisioned separately; model quality measurements remain separate from SDK correctness.

Install the published SDK version for your registry:

python -m pip install 'datafog-core==1.6.0'
npm install --save-exact @datafog/node@1.6.0
cargo add datafog-core@=1.6.0 --features models

For GLiNER2, install its optional dependencies in the Python environment used by the runner:

python -m pip install 'datafog-core[gliner2]==1.6.0'

Embedded name and address detection

EmbeddedCnnDetector carries the pinned statements-v1 CNN in the extension itself: no model download, no files, no subprocess and no inference runtime. It is the same detector the browser build embeds and returns the same ModelScanResult contract as ModelSession.

from datafog_core import EmbeddedCnnDetector

detector = EmbeddedCnnDetector()          # authenticates the embedded weights once
result = detector.scan(text, {"entities": ["PERSON", "ADDRESS", "EMAIL"]})

Limits are 65,536 input bytes and 8,192 tokens per request and 1,024 findings. Inference is synchronous and in-process, so ModelCancellation cannot interrupt it; keep a detector per worker thread. scan_model returns model-only findings, and EmbeddedCnnDetector.scan_disabled validates the same selection with no inference. Embedded CNN reference →

GLiNER2 supports the PII checkpoint and compatible general-purpose span models with caller-defined labels. The GLiNER2 runner ships in the Python package and also serves Node.js and Rust callers. Download and verify model files separately, then use ModelSession.open, text scan, and close. Reuse sessions across calls. Both backends return consistent results and errors, with cancellation and cleanup support.

datafog setup and session API → · GLiNER2 setup →

Documentation and development

For existing datafog Python applications, follow the migration guide for changes to imports, results, and transformations.

For Rust development, run:

cargo fmt --all --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace --all-features

See the development guide for the repository layout and Python, Node.js, and WASM package checks.

License

MIT. Built by datafog.

Metadata

Release files for datafog-core 1.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for datafog-core 1.6.0
File Size Uploaded Provenance Actions
datafog_core-1.6.0.tar.gz 1.3 MB With provenance Details for datafog_core-1.6.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for datafog-core 1.6.0
File Actions
datafog_core-1.6.0-cp310-abi3-win_arm64.whl CPython 3.10 abi3 Windows ARM64 Details for datafog_core-1.6.0-cp310-abi3-win_arm64.whl
datafog_core-1.6.0-cp310-abi3-win_amd64.whl CPython 3.10 abi3 Windows x86-64 Details for datafog_core-1.6.0-cp310-abi3-win_amd64.whl
datafog_core-1.6.0-cp310-abi3-musllinux_1_2_x86_64.whl CPython 3.10 abi3 Linux musl 1.2+ x86-64 Details for datafog_core-1.6.0-cp310-abi3-musllinux_1_2_x86_64.whl
datafog_core-1.6.0-cp310-abi3-musllinux_1_2_aarch64.whl CPython 3.10 abi3 Linux musl 1.2+ ARM64 Details for datafog_core-1.6.0-cp310-abi3-musllinux_1_2_aarch64.whl
datafog_core-1.6.0-cp310-abi3-manylinux_2_28_x86_64.whl CPython 3.10 abi3 Linux glibc 2.28+ x86-64 Details for datafog_core-1.6.0-cp310-abi3-manylinux_2_28_x86_64.whl
datafog_core-1.6.0-cp310-abi3-manylinux_2_28_s390x.whl CPython 3.10 abi3 Linux glibc 2.28+ IBM System/390x Details for datafog_core-1.6.0-cp310-abi3-manylinux_2_28_s390x.whl
datafog_core-1.6.0-cp310-abi3-manylinux_2_28_ppc64le.whl CPython 3.10 abi3 Linux glibc 2.28+ PowerPC 64-le Details for datafog_core-1.6.0-cp310-abi3-manylinux_2_28_ppc64le.whl
datafog_core-1.6.0-cp310-abi3-manylinux_2_28_aarch64.whl CPython 3.10 abi3 Linux glibc 2.28+ ARM64 Details for datafog_core-1.6.0-cp310-abi3-manylinux_2_28_aarch64.whl
datafog_core-1.6.0-cp310-abi3-macosx_11_0_arm64.whl CPython 3.10 abi3 macOS 11.0+ ARM64 Details for datafog_core-1.6.0-cp310-abi3-macosx_11_0_arm64.whl
datafog_core-1.6.0-cp310-abi3-macosx_10_12_x86_64.whl CPython 3.10 abi3 macOS 10.12+ x86-64 Details for datafog_core-1.6.0-cp310-abi3-macosx_10_12_x86_64.whl

Total release size: 36.5 MB

Release files / datafog_core-1.6.0.tar.gz

Download URL datafog_core-1.6.0.tar.gz
Size 1.3 MB
Tags Source
SHA-256 checksum
How to use checksums
4ab0faa943f0d4ad80ce803a56e69632d8c8084e48337fa9540b5a64f1ad701b
BLAKE2b-256 checksum
How to use checksums
819145b48bd9d2117ebd591ee420b3d2e35477223f3b9a413b961fcabbf3664f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / datafog_core-1.6.0-cp310-abi3-win_arm64.whl

Download URL datafog_core-1.6.0-cp310-abi3-win_arm64.whl
Size 3.0 MB
Tags CPython 3.10 Windows ARM64 abi3
SHA-256 checksum
How to use checksums
868364ab6b3b32ed8c98c794b4fecffd7125882e4ff5ae23171040b7d5c6bd24
BLAKE2b-256 checksum
How to use checksums
eed34bddac574fc5b8b140c56b113e3ee3996a8f6727940da852f42d74dd7da2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / datafog_core-1.6.0-cp310-abi3-win_amd64.whl

Download URL datafog_core-1.6.0-cp310-abi3-win_amd64.whl
Size 3.2 MB
Tags CPython 3.10 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
97540f8a6bc76b5fada9f990c44832460cdbb603cd3cd095d9d64e82ce4a9b69
BLAKE2b-256 checksum
How to use checksums
b6ca32681036cbecd6d88b5faba27eb585859927dbc102b20dabd7bbb0fcafce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / datafog_core-1.6.0-cp310-abi3-musllinux_1_2_x86_64.whl

Download URL datafog_core-1.6.0-cp310-abi3-musllinux_1_2_x86_64.whl
Size 3.9 MB
Tags CPython 3.10 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
9c039a7f58432730b9bfeff8861fbf24563c511ad525cca03d3f763ac7a8f840
BLAKE2b-256 checksum
How to use checksums
45430d4063fd98bc2699d84e573c7576a67e5b026d8a8a3e0a71d9fb94633310
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / datafog_core-1.6.0-cp310-abi3-musllinux_1_2_aarch64.whl

Download URL datafog_core-1.6.0-cp310-abi3-musllinux_1_2_aarch64.whl
Size 3.7 MB
Tags CPython 3.10 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
36db61b69da7c77cb2a7ebdcad5c0bc76b3a728821b056452554a12e5d230a2d
BLAKE2b-256 checksum
How to use checksums
e6e7fe18db0f71721e9b45816fdc557473fdb5abfa382089d7cf575e6c38523d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / datafog_core-1.6.0-cp310-abi3-manylinux_2_28_x86_64.whl

Download URL datafog_core-1.6.0-cp310-abi3-manylinux_2_28_x86_64.whl
Size 3.7 MB
Tags CPython 3.10 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
79dc4fc3285b98fd14653b83fb335ad8014b4638ada171d061cd971178a26c19
BLAKE2b-256 checksum
How to use checksums
23361d3e5c2c00a65b54346d8d068918de088155022828e8703839ece6cf69ed
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / datafog_core-1.6.0-cp310-abi3-manylinux_2_28_s390x.whl

Download URL datafog_core-1.6.0-cp310-abi3-manylinux_2_28_s390x.whl
Size 3.6 MB
Tags CPython 3.10 Linux glibc 2.28+ IBM System/390x abi3
SHA-256 checksum
How to use checksums
7bb5a1a0c7895f1c10fc360f3a860143808a251e71447fd8a4f05e78f1b1bc47
BLAKE2b-256 checksum
How to use checksums
c59c433b64932018b3886e98feb78f126abdf57978cffdf9ecffaad9f2bd7312
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / datafog_core-1.6.0-cp310-abi3-manylinux_2_28_ppc64le.whl

Download URL datafog_core-1.6.0-cp310-abi3-manylinux_2_28_ppc64le.whl
Size 3.9 MB
Tags CPython 3.10 Linux glibc 2.28+ PowerPC 64-le abi3
SHA-256 checksum
How to use checksums
ab51a1e21e7adbcc5e3a65f0c3205227ca9410769d9b116b2448e8bba416db09
BLAKE2b-256 checksum
How to use checksums
f4fed599c4f17703d8ad39bd298560094c41bcd6c61fd26159b8b036ba1d7297
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / datafog_core-1.6.0-cp310-abi3-manylinux_2_28_aarch64.whl

Download URL datafog_core-1.6.0-cp310-abi3-manylinux_2_28_aarch64.whl
Size 3.5 MB
Tags CPython 3.10 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
47f7a42d495525b8adf65ac4e4a6690dc2c98ba054e9125b10bdfe0e569ee902
BLAKE2b-256 checksum
How to use checksums
0e28aefa1bcf10bbb4d477eb136cea111512f86019e327115f81abf94209b529
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / datafog_core-1.6.0-cp310-abi3-macosx_11_0_arm64.whl

Download URL datafog_core-1.6.0-cp310-abi3-macosx_11_0_arm64.whl
Size 3.3 MB
Tags CPython 3.10 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3d3122da80a9b6b244e30440ea28ae4e1054b58bf11a91902bc92d8d11fb931c
BLAKE2b-256 checksum
How to use checksums
bf2ad48784fa1e7457898351b83e9fbf22ae1029be65541a6c1df63828f0d762
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / datafog_core-1.6.0-cp310-abi3-macosx_10_12_x86_64.whl

Download URL datafog_core-1.6.0-cp310-abi3-macosx_10_12_x86_64.whl
Size 3.4 MB
Tags CPython 3.10 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
c105c8481932af2e40d0ac9e6e27c3c9a8d3f83ae2e45b57a2af2c8e8ae62c6a
BLAKE2b-256 checksum
How to use checksums
77d6e6bff6319e5c611acd05cd716a9e9687ae803177cfc6dd347e3866291f9d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Security for datafog-core 1.6.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 11 files in this release have been uploaded with provenance metadata.

Select from 11 files

Attestation for datafog_core-1.6.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.6.0 This release

11 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page