Audit
One audit service and event log for every action.
RivetCore\Audit
Beta v1.0.0-rc.60 GNU General Public License v3.0 PHP 8.2 or later
Edition-neutral PHP services (audit, background jobs, Redis helpers, the MCP pipeline, webhooks, automation, workflows and service-management building blocks) kept in one library so an improvement lands in both products.
A library for PHP developers and for the two products, not an application you install. Below 1.0 its interfaces can still change between releases, so pin a version. To run software today, choose RivetIT or RivetMSP.
Departments · interface · training · Odoo
Clients · interface · billing
Production release on January 1, 2027. Rivet Core is in beta until then. See the roadmap.
Why it exists
RivetIT and RivetMSP need the same plumbing. We keep it in one library, so we fix it once and both products get the fix.
A bug we fix or a feature we add in Rivet Core ships to RivetIT and RivetMSP together. Without it, we would write and fix everything twice.
We are bringing RivetIT's service-management features across to RivetMSP. Building them once in the core is how we do that without copying code.
The core has its own automated tests and security checks, so both products rely on code that was checked once, in the open.
You do not need to think about Rivet Core to use RivetIT or RivetMSP. It matters if you build or extend an edition yourself. It is in beta, like the products.
One audit service and event log for every action.
RivetCore\Audit
Locks, rate limiting, cron guards and Redis admin tools.
RivetCore\Redis, Health
An allowlisted job runner with "run now" in the admin area.
RivetCore\Cron
An atomic job queue, safe for concurrent workers.
RivetCore\Jobs
Configuration and a kill switch for the MCP pipeline.
RivetCore\Mcp
Problem and change services with status machines.
RivetCore\ITSM
24 platform presets, 13 formats, signed delivery and a 113-event catalog.
RivetCore\Webhooks
Rule matching and evaluation. Your edition runs the actions.
RivetCore\Automation
Templates and runs you can complete, skip, reopen or cancel.
RivetCore\Workflow
Prunes old audit events, deliveries and finished jobs.
RivetCore\Retention
Word and PDF converters and a safe article renderer.
RivetCore\KB, Knowledge
In development: enrollment, signed jobs, inventory, patching and software deployment. Off by default.
RivetCore\Rmm
The interface shell, billing, the client or department model, training and Odoo stay in each product. Documentation
Get started
Add the repository, require a pinned version, then wire the pieces your edition provides.
DatabaseInterface over your existing connection.MigrationRunner from your updater. It keeps its own migration state, separate from your product's database version.Needs PHP 8.2 or later plus Guzzle, Predis and psr/simple-cache. Tests run in CI against MariaDB and Redis.
composer config repositories.rivet-core vcs https://github.com/TheTractorHacker/rivet-core
composer require rivet/rivet-core:^1.0
{
"repositories": [
{
"type": "vcs",
"url": "https://github.com/TheTractorHacker/rivet-core"
}
],
"require": {
"rivet/rivet-core": "^1.0"
}
}
Package rivet/rivet-core.
v1.0.0-rc.60 v1.0.0-rc.59 v1.0.0-rc.58 v1.0.0-rc.57 v1.0.0-rc.56 v1.0.0-rc.55 v1.0.0-rc.54 v1.0.0-rc.53
Latest
Additive only: no existing signature, constant or table changed. Core ships the shared logic; each edition adds the public endpoint, settings page, incident table and ticket adapter (docs/design/edition-prompts-inbound-monitoring.md).
RivetCore\Monitoring\Inbound (@api). UptimeKumaPayload (strict parser of the default Uptime Kuma webhook JSON: 64 KB cap, field length caps, control and bidi characters stripped, null heartbeat = test notification, typed PayloadRejection instead of exceptions), PayloadParserInterface (for further monitors), InboundEvent, MonitorStatus.IncidentEngine with EngineConfig and EngineOutcome: one incident per source + monitor; DOWN opens a ticket (after N DOWNs or a minimum duration, default 1 / off), repeat DOWNs add at most one note per interval (30 min), UP adds a recovery note with the outage duration and resolves; PENDING and MAINTENANCE are ignored; a ticket a person resolved is never reopened; duplicate and out-of-order deliveries are no-ops; a flap guard (6 opens per monitor per hour) turns extra opens into notes. Unmapped monitors go to the default client or "unassigned", never guessed.TicketGatewayInterface, IncidentStoreInterface (with Incident), MonitorClientMapInterface (with MonitorTarget, TicketRequest), RateLimiterInterface. Reference implementations InMemoryTicketGateway, InMemoryIncidentStore, InMemoryMonitorClientMap and conformance cases TicketGatewayConformanceTestCase, IncidentStoreConformanceTestCase in RivetCore\Testing.InboundAuthenticator and InboundHandler::handle(array $headers, string $rawBody, string $remoteIp): InboundResult. Shared secret from X-Webhook-Secret or Authorization: Bearer, compared with hash_equals over SHA-256 digests; fails closed (no, empty or under-16-character secret rejects everything); several secrets at once for rotation; rate-limit hook; responses carry fixed tokens and a ticket id only; the raw body is never logged.docs/modules/inbound-monitoring.md (Uptime Kuma setup), docs/design/edition-prompts-inbound-monitoring.md. Regenerated docs/api-surface.md, tests/api-surface.json, docs/PUBLIC-API.md.Live from the repository's issues. 63 of 74 done.
Read the architecture notes, try a version in an edition, or open an issue.