PHPackages                             zerig/report - 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. [PDF & Document Generation](/categories/documents)
4. /
5. zerig/report

ActiveLibrary[PDF & Document Generation](/categories/documents)

zerig/report
============

Report user about what happend.

v1.1.0(6y ago)0241MITPHPPHP >=5.6.0

Since Apr 28Pushed 6y ago1 watchersCompare

[ Source](https://github.com/Zerig/report)[ Packagist](https://packagist.org/packages/zerig/report)[ RSS](/packages/zerig-report/feed)WikiDiscussions master Synced 6d ago

READMEChangelogDependencies (1)Versions (8)Used By (1)

REPORT
======

[](#report)

Report namespace set and collect **action reports**, which should be shown by visitor. Without this user cannot know what happend. If his action was succesfull or failed.\\n For example: 'Item was successfully updated'.

rData($array)
-------------

[](#rdataarray)

Instance of this class represents one action report. There is everything what visitor needs to see.

```
\Report\rDATA([
	"group" => "action",               // GROUP of REPORT => mysql, file, form, ...
	"state" => "fail",                 // How action END => success, info, fail
	"msg"   => "This action failed.",  // Message what happend
	"type"  => 0,                      // CODE or NAME of GROUP action => 1062, insert, upload,...
	"num"   => 1                       // How many items was in action
]);
```

GROUP
-----

[](#group)

Every group report has special class inherits `\Report\Action`. That is because every goup need to be solved differently.

- **Report\\Mysql** should set report about *DB* acions (insert, update, delete,...)
- **Report\\File** should set report about acions with *FILES* (delete, upload, move,...)
- **Report\\Form** should set report about *FORM* actions (input is empty,...)

STATE
-----

[](#state)

Every group report has special class inherits `\Report\Action`. That is because every goup need to be solved differently.

- **success** when action was successfull
- **info** when you want inform user about something
- **fail** when action failed

MSG
---

[](#msg)

Text which will be shown user after his action. They are saved in JSON file in the same folder as method.\\n

```
{
	"action": {
		"fail":{
			"0": "Something goes WRONG!",
			"duplicit": "0% 1% already exist"
		},
		"info":{
			"0": "Nothig is happend."
		},
		"success":{
			"0": "Everything happend successfully."
		}
	}
}
```

1. First level say which `group` of answers you want
2. Second level is `state`: How action happend
3. Third level `type` say what specifically happend. But if that `type` is not found it will use `type = 0`

More information in class [\\REPORT\\ACTION](https://github.com/Zerig/report/blob/master/ACTION.md)

TYPE
----

[](#type)

Say what specifically happend

- duplicit item
- file exist
- file has no permission to remove

They can be as a shortcut `'duplicit'`, or code `'1062'`. And if `type` is not found in **JSON** it will use `type = 0`.

NUM
---

[](#num)

Number of items in action. How manz items was changed during MYSQL query. How many files was uploaded...

###  Health Score

25

—

LowBetter than 37% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity56

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

Total

7

Last Release

2204d ago

### Community

Maintainers

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

---

Top Contributors

[![Zerig](https://avatars.githubusercontent.com/u/17721175?v=4)](https://github.com/Zerig "Zerig (51 commits)")

---

Tags

report

### Embed Badge

![Health badge](/badges/zerig-report/health.svg)

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

###  Alternatives

[jimmyjs/laravel-report-generator

Rapidly Generate Simple Pdf & Excel Report on Laravel 5 (Using Barryvdh/DomPdf or Barryvdh/laravel-snappy & maatwebsite/excel)

580157.4k1](/packages/jimmyjs-laravel-report-generator)[drutiny/drutiny

This is a generic Drupal 7 and Drupal 8 site auditing and optional remediation tool.

132122.2k17](/packages/drutiny-drutiny)[scheb/tombstone-analyzer

Generates reports based on the logs from scheb/tombstone-logger

28378.1k2](/packages/scheb-tombstone-analyzer)[quilhasoft/jasperphp

Pure PHP library to read JRXML files made with 'JasperSoft Studio' and generate reports in PDF

7542.4k1](/packages/quilhasoft-jasperphp)[aspose-cloud/aspose-words-cloud

Open, generate, edit, split, merge, compare and convert Word documents. Integrate Cloud API into your solutions to manipulate documents. Convert PDF to Word (DOC, DOCX, ODT, RTF and HTML) and in the opposite direction.

32157.4k](/packages/aspose-cloud-aspose-words-cloud)[silverstripe/securityreport

Generates a security and access report for CMS users

10292.1k4](/packages/silverstripe-securityreport)

PHPackages © 2026

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