PHPackages                             spitfire/exception - 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. spitfire/exception

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

spitfire/exception
==================

Exception interfaces for spitfire

0.1.5(3y ago)01.4k5LGPL-3.0+PHP

Since Feb 17Pushed 1y ago1 watchersCompare

[ Source](https://github.com/spitfire-php/exceptions)[ Packagist](https://packagist.org/packages/spitfire/exception)[ RSS](/packages/spitfire-exception/feed)WikiDiscussions master Synced 1w ago

READMEChangelogDependenciesVersions (7)Used By (5)

SPITFIRE EXCEPTIONS
===================

[](#spitfire-exceptions)

Spitfire provides a very barebones set of basic exceptions to create a versatile and extensible layer for packages to extend upon. It is not intended to be a thorough and semantic description of the errors that can originate, but a good baseline for inheriting products to work with.

There's two types of exceptions scopes:

1. System: These exceptions help report system errors and issues that the user is neither responsible for, nor should be interested in.
2. User: Report issues that are relevant to the user, like a missing permission or a quota being exceeded.

For each of these categories, Spitfire defines three types of permissions:

1. Not Found Exceptions
2. Permissions Exceptions
3. Application exceptions

These indicate whether the system ran into an issue that is rooted within a resource being either unavailable or not existing, a resource being locked and the application or user not having enough authority to unlock them, and everything else.

The idea behind these is to have each package inheriting from these define their own exceptions that can be caught and managed, while making it comfortable for an application developer to generate a set of just a few pages to report errors that the system may be running into.

###  Health Score

27

—

LowBetter than 49% of packages

Maintenance29

Infrequent updates — may be unmaintained

Popularity18

Limited adoption so far

Community13

Small or concentrated contributor base

Maturity40

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 ~16 days

Recently: every ~0 days

Total

6

Last Release

1104d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/b98c0aaba6758a642cd9f8567ace81542988b07c61ed9e5cd889b2f7a10c9c3e?d=identicon)[Csharp](/maintainers/Csharp)

---

Top Contributors

[![Csardelacal](https://avatars.githubusercontent.com/u/1152823?v=4)](https://github.com/Csardelacal "Csardelacal (2 commits)")

### Embed Badge

![Health badge](/badges/spitfire-exception/health.svg)

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

###  Alternatives

[stuttter/wp-user-profiles

A sophisticated way to edit users in WordPress

11219.3k1](/packages/stuttter-wp-user-profiles)[fof/analytics

Tracks analytics using Google Analytics, Google Optimize/GTM and Matomo

3543.1k](/packages/fof-analytics)[chrico/wp-fields

Package which provides some re-usable fields for WordPress.

1981.2k](/packages/chrico-wp-fields)[aertmann/history

An improved history backend module for Neos

1070.2k](/packages/aertmann-history)

PHPackages © 2026

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