PHPackages                             f500/integritycheck - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. f500/integritycheck

AbandonedArchivedLibrary[Utility & Helpers](/categories/utility)

f500/integritycheck
===================

Provides a interfaces for building integrity checks for your app

v0.0.5(9y ago)028MITPHP

Since Jul 17Pushed 9y agoCompare

[ Source](https://github.com/f500/integritycheck)[ Packagist](https://packagist.org/packages/f500/integritycheck)[ RSS](/packages/f500-integritycheck/feed)WikiDiscussions master Synced 4w ago

READMEChangelogDependenciesVersions (6)Used By (0)

integritycheck
==============

[](#integritycheck)

This repo provides some interfaces to build integrity checks for your application.

Integrity checks are somewhere between integration tests (that should ensure the correct functionality of your app) and monitoring (that should ensure the availability of your app).

They consist of an `investigation` that can detect some invalid state (usually of dsata), and a `resolution` that can resolve the situation. There are three types of resolution:

- Automatic: this solves the detected problem by running queries, code or anything else.
- Manual: maybe the resolution is dangerous or impossible to deduce, this is a description of how to resolve the detected situation.
- NotImplemented: this allows checks to be built without knowing the resolutions but still keeping track of which integrity checks still need more work.

An example of an integrity check could be:

- Investigation: query a datastore for articles with a "published" state where "publishUntil" is in the past

Examples of resolutions could be:

- AutomaticResolution: unpublish the articles in question
- ManualResolution: call Anton from the news division on 1234 and ask which articles need to be de-published

Obviously you would also want to check your de-publication cronjobs in such a case.

###  Health Score

25

—

LowBetter than 35% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity7

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity57

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

5

Last Release

3636d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/6752675?v=4)[F500](/maintainers/f500)[@f500](https://github.com/f500)

---

Top Contributors

[![ramondelafuente](https://avatars.githubusercontent.com/u/668391?v=4)](https://github.com/ramondelafuente "ramondelafuente (6 commits)")

### Embed Badge

![Health badge](/badges/f500-integritycheck/health.svg)

```
[![Health](https://phpackages.com/badges/f500-integritycheck/health.svg)](https://phpackages.com/packages/f500-integritycheck)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)