Download the PHP package fissible/attest-laravel without Composer

On this page you can find all versions of the php package fissible/attest-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package attest-laravel

fissible/attest-laravel

Laravel adapter for fissible/attest: Eloquent storage, Artisan commands, queue-ready anchoring, and events.

Status: Stable — v1.0+. The public API (types marked @api) follows semantic versioning; see fissible/attest 1.x core. Anchoring inherits core's @experimental status in 1.x.


What is this, in plain terms?

This package is the Laravel integration for fissible/attest, a tamper-evident logbook for the important things your application does — contract approvals, publishes, permission grants, anything you might one day need to prove happened and prove wasn't edited afterward.

The core library handles the cryptography (each event is signed and chained, so any later tampering is detectable, and batches can be "notarized" against the Bitcoin blockchain to prove when they existed). This package wires all of that into Laravel so you barely have to think about it:

New to attest? Read the core README first for the plain-language "what and why," including the worked dispute example. This page assumes you want it inside a Laravel app.

The 30-second example

Record an event when something important happens:

Later, prove that chain is intact and signed by a key you trust:

A clean chain exits 0. A tampered or unsigned chain fails — so "the log wasn't edited" stops being something you ask people to take on faith.

Everything below is detail you can read when you need it.


Install

Requires PHP ^8.2 and Laravel 12 or 13. (Laravel 13 requires PHP ^8.3; PHP 8.2 is supported on Laravel 12.) Migrations also auto-load if you do not want to publish them.

Configure

Set the attest database connection and signing key environment variables:

Useful operational defaults:

Header-provider lookups use a container-bound Psr\Http\Client\ClientInterface when one is bound. The container's PSR-17 request and stream factories are used when available, otherwise guzzlehttp/psr7 supplies those factories.

OpenTimestamps anchoring and Bitcoin header verification use optional PSR-18/PSR-7 wiring from core. This package suggests guzzlehttp/guzzle and guzzlehttp/psr7; install them when you want calendar or header-provider commands to create HTTP clients from config.

Chains, and why the examples say tenant:5

A chain is one append-only, hash-linked sequence. Attest::chain('...') names it, and the name is your convention — attest never parses it. Everything that matters is scoped to a chain: sequence numbers, the hash link, the write lock, and verification. Break one chain and the others are untouched; verify one chain and you have said nothing about the rest.

That scoping is why a multi-tenant application — one deployment serving several customers, organizations, or workspaces that must not see each other's data — usually opens one chain per tenant rather than one chain for everything:

tenant:5 is just that convention written out: a chain holding tenant 5's evidence. Use whatever reads clearly for your domain — org:acme, workspace:42, updater:global for something that is genuinely global. Single-tenant applications can happily use one chain per concern (billing, contracts) instead; nothing here requires tenancy.

Separately, record() takes an optional tenant value. That is a field on the signed envelope and an indexed column, not a chain selector — it answers "which tenant did this concern?" for queries that cross chains, and it is what lets a shared chain stay queryable per tenant. The two are independent: use the chain id for isolation, the field for attribution.

Record

Each record() opens a per-chain write lock, reads the chain tail, builds an AppendContext, signs the envelope with the configured Ed25519 key, validates the context, persists into attest_envelopes, and dispatches an EnvelopeRecorded event after the transaction commits.

Query by correlation, subject, or tenant

record() accepts optional subject, correlation, and tenant values. They are part of the signed envelope, and they are also projected into indexed columns so you can find envelopes without decoding every row in a chain:

forCorrelation() and forSubject() return oldest-first, ordered by created_at with envelope_id breaking ties — sequence only orders within a single chain. Neither is chain-scoped: a correlation id is assigned by the writing application, so an application that shards one chain per tenant still gets a single answer across chains.

Correlation ids are unique only by your own convention. If you cannot rely on that convention across tenants, scope the query: AttestEnvelope::query()->forTenant('acme')->forCorrelation($id).

These columns are a projection, never verifier trust input. raw_envelope holds the only signed bytes, and that is what attest:verify reads. Editing a projection column cannot forge evidence or make a broken chain verify — but blanking one can hide a row from these queries while the chain still verifies clean. attest:integrity:audit compares every projection column back against the raw envelope and reports drift, so run it on a schedule if you rely on these queries for audit answers. When completeness matters more than latency, read the chain.

Import JSONL

Use GenericJsonlImporter when an application already has append-only JSONL and wants to replay it into an attest chain without duplicate envelopes:

importer() is the durable marker namespace stored in attest_import_markers. Include the logical importer, upstream source/feed identity, and schema version; do not use only the PHP class name. contentHashFor() must return a stable lower-case SHA-256 digest for the logical source record, not a line number or byte offset.

The importer uses ChainStore::append() directly and writes the marker inside the append callback. With EloquentChainStore, the marker and envelope append share one transaction, so a failed append does not strand a marker. Reruns skip existing markers; malformed records fail fast by default. Pass new JsonlImportOptions(continueOnError: true) to collect diagnostics and continue past bad lines.

Bridges for a specific upstream log belong in the application that owns that log — a sidecar over its existing JSONL, not something this package can know the shape of. Only the generic importer primitives ship here.

Anchor

Anchor a known range immediately:

Dispatch the queueable AnchorPendingBatch instead of anchoring inline:

The package does not auto-register schedules. Add scheduling in your app when you want periodic anchoring:

For OpenTimestamps:

Upgrade pending OpenTimestamps receipts:

Verify

Verify chain integrity and trusted signatures:

Require an anchor threshold:

Accepted --min-anchor values are local_only, pending, upgraded_no_headers, remote_header_confirmed, and bitcoin_verified.

For programmatic verification, resolve the stable verifier from the container:

Bundles

Export a portable proof bundle:

Verify a bundle:

Claimed keys included in bundles are informational. They are never trusted automatically by attest:bundle:verify.

Integrity Audit

Audit Eloquent read-side index columns against raw canonical envelopes:

Exit codes are 0 for clean, 1 for invalid options, and 4 for detected drift.

Database Support

License

MIT


All versions of attest-laravel with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
fissible/attest Version ^1.1
illuminate/bus Version ^12.0 || ^13.0
illuminate/console Version ^12.0 || ^13.0
illuminate/database Version ^12.0 || ^13.0
illuminate/queue Version ^12.0 || ^13.0
illuminate/support Version ^12.0 || ^13.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package fissible/attest-laravel contains the following files

Loading the files please wait ...