gemvc/helper

GEMVC helper utilities: ProjectHelper, CryptHelper, type checking, file/image helpers, and more.

Maintainers

Package info

github.com/gemvc/helper

pkg:composer/gemvc/helper

Statistics

Installs: 2

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

Security

Advisories: 0

Aikido package health analysis

v1.0.1 2026-06-06 11:18 UTC

Requires

Requires (Dev)

Suggests

  • ext-gd: Required for ImageHelper WebP conversion
  • ext-openssl: Required for FileHelper encryption and CryptHelper

MIT 06b0107a13bb679c4f039372385a0fa85979713f

  • Ali Khorsandfard <ali.khorsandfard.woop@gmail.com>

phphelperutilitiesgemvc

This package is auto-updated.

Last update: 2026-06-06 11:18:55 UTC

README

Helper utilities for the GEMVC framework.

Composer package: gemvc/helper
GitHub repo: gemvc/helper

WARNING

This is an internal GEMVC ecosystem package. It is designed to be installed with gemvc/library, not on its own.

Do not run composer require gemvc/helper in a generic PHP project expecting a standalone utility library — several classes depend on gemvc/library (HTTP layer, system page paths, etc.) and may not work without the full framework in vendor/.

Supported install path: composer require gemvc/library (which pulls in gemvc/helper automatically).

Installation

Installed automatically with the framework:

composer require gemvc/library

gemvc/library requires gemvc/helper — you do not need a separate install in normal apps.

Classes

Class Purpose
ProjectHelper Project root, .env, URLs, library paths
CryptHelper Password hashing (Argon2i)
TypeChecker / TypeHelper Request schema type validation
FileHelper AES-256-CBC file encryption
ImageHelper WebP conversion
JsonHelper, StringHelper, WebHelper General utilities
ServerMonitorHelper, NetworkHelper Monitoring metrics

Namespace: Gemvc\Helper\ (unchanged from monorepo layout).

Pairing with gemvc/library (no circular Composer dependency)

  • gemvc/library requires gemvc/helper — normal app install path
  • gemvc/helper does NOT require gemvc/library — avoids library → helper → library cycle

Some classes (ChatGptClient, legacy TraceKitToolkit) use Gemvc\Http\* from gemvc/library at runtime in real apps. When both packages are in vendor/, autoload resolves the real HTTP classes from the library.

This package ships HTTP stubs under stubs/ for standalone PHPUnit/PHPStan only (autoload-dev). They are not used when the package is installed as a dependency of gemvc/library.

Development

composer install
composer test
composer phpstan

Release workflow (v1)

  1. Copy this folder into a clone of github.com/gemvc/helper
  2. Tag and publish 1.0.0 on Packagist
  3. Update gemvc/library to require gemvc/helper: ^1.0 and remove src/helper/

v1.0 changes

  • Lift-and-shift from gemvc/library/src/helper/ (14 files, same namespace)
  • ProjectHelper::getLibrarySystemPagesPath() resolves gemvc/library via InstalledVersions

Future cleanup (TraceKit legacy removal, etc.) happens in this package only.

Push to GitHub (your workflow)

  1. Create repo github.com/gemvc/helper
  2. Copy all contents of this staging folder into the clone (repo root = package root; local folder name gemvc-helper/ in the monorepo is only for staging)
  3. composer install then composer test && composer phpstan (PHPStan has 4 pre-existing issues carried from library — same as src/helper/ today)
  4. Tag v1.0.0 and publish to Packagist as gemvc/helper
  5. In gemvc/library release 5.8.1: add "gemvc/helper": "^1.0", remove src/helper/ and Gemvc\Helper\ autoload, run composer update and full test suite