Download the PHP package wazum/composer-fanfare without Composer

On this page you can find all versions of the php package wazum/composer-fanfare. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package composer-fanfare

composer-fanfare

Latest Version CI PHP Version

Display a colored ASCII banner after composer install / composer update.

[^1]

Every composer install ends the same boring way: autoload files generated, then silence.

composer-fanfare replaces that with a project-specific full-stop — a colored ASCII banner that confirms which project just finished and lets you convey your own message: "Made with ❤️ by the maintainers".

Useful when you're proud of your work, juggle multiple repos, or just want a little fun after the thousandth composer install.

Stays respectful: silent in CI, plain in non-TTY shells, suppressed under --quiet.

Install

[!IMPORTANT] Composer 2.2+ asks for plugin approval on first run. Interactive shells prompt you; in CI or non-interactive setups, allow it explicitly:

Configure

Drop a plain-text template anywhere in your project (e.g. art/banner.txt) and reference it from composer.json:

[!NOTE] The banner falls back to plain text when NO_COLOR is set or output isn't a TTY. Composer's --quiet mode suppresses it entirely via the IO layer. If any banner line is wider than the current terminal, the banner is skipped silently to avoid wrapping artefacts.

Disabling

Skip the banner for a single run by setting COMPOSER_FANFARE=0 inline:

Or disable it globally for the current shell or CI environment:

Setting values from the CLI

If you'd rather not hand-edit composer.json, every key can be set with composer config:

Booleans and arrays need --json so the value is stored with the right type:

Remove a key with --unset:

Color depth

Truecolor escapes are emitted by default. The renderer downgrades automatically based on COLORTERM and TERM:

Detected support Trigger Output
24-bit COLORTERM=truecolor / 24bit, or any modern terminal \033[38;2;R;G;Bm
256-color TERM matching *-256color \033[38;5;Nm (xterm 6×6×6 cube + 24-step grayscale ramp)
16-color TERM=ansi / vt100 / linux nearest-neighbor mapping to the standard ANSI palette
Plain NO_COLOR=1, TERM=dumb, or non-TTY banner content rendered without escapes

Preset gallery

plain
aurora
catppuccin
doom
dracula
fire
gruvbox
iceberg
matrix
monokai
nord
ocean
pride
solarized
sunset
synthwave

Preview

Pick a preset without running an install:

--direction and --transform accept the same values as the matching extra.fanfare keys. The preview uses your project's configured extra.fanfare.template if there is one, otherwise it falls back to a small built-in banner.

Creating a template

The template is any plain-text file. For large ASCII letters from a word, the classic tool is figlet:

Try other fonts with -f slant, -f big, -f small, etc.; figlist lists what's installed. Prefer a browser? patorjk.com/software/taag is a popular generator with the same fonts.

Another option is toilet, which offers its own font set and can be useful for compact banner styles:

[!NOTE] Banner output relies on the font your terminal renders monospaced text in. Block-shading glyphs (█▀▄░ from pagga/smblock/block) and box-drawing glyphs (┏━┓┃ from future/emboss) are covered by every modern terminal font (JetBrains Mono, Fira Code, Cascadia, Hack, Menlo). Sparser ranges like braille (⡠⢀⣀ from smbraille) are not — if a glyph shows up as , switch to a font with wider Unicode coverage (DejaVu Sans Mono, Cascadia Code, Iosevka).

License

MIT.

[^1]: The company names, project names, and email addresses shown in the demo (Atelier Prime, harbor sync, Neon District, meridian labs, lumen forge, etc.) are fictional — invented to illustrate the kind of personal banner you might write for your own project.


All versions of composer-fanfare with dependencies

PHP Build Version
Package Version
Requires php Version >=8.2
ext-mbstring Version *
composer-plugin-api Version ^2.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wazum/composer-fanfare contains the following files

Loading the files please wait ...