PHPackages                             brediweb/banner - 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. brediweb/banner

ActiveLibrary

brediweb/banner
===============

0356↓100%PHP

Since Nov 4Pushed 4y ago1 watchersCompare

[ Source](https://github.com/moraismarcelo/brediweb-banner)[ Packagist](https://packagist.org/packages/brediweb/banner)[ RSS](/packages/brediweb-banner/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

1 - no arquivo composer.json do Laravel, coloque:

```
"repositories": [
    {
        "type": "vcs",
        "url": "https://gitlab.com/pacotes-bredi/bredi-banner"
    }
]
```

2 - na linha de comando digite `composer require bredi/banner`

se o git exigir, coloque seu login e senha do gitlab para poder baixar o pacote.

3 - na linha de comando: `php artisan migrate`

4 - rode o seeder para criar as transações: `php artisan db:seed --class=Brediweb\\BrediBanner\\Database\\Seeders\\BannersTableSeeder`

O pacote vem com algumas funções para facilitar

1 - Recuperando os banners ativos no seu controller:

```
//Apenas esta linha já retorna os registros
$banners = (new \Brediweb\BrediBanner\Repository\BannerRepository)->getBannersAtivos();

```

exportando arquivo config do pacote BrediBanner: `php artisan vendor:publish --tag=banner-config`

exportando as views do pacote BrediBanner: `php artisan vendor:publish --tag=bredi-banner`

API
===

[](#api)

Recuperar banners ativos por api

`GET => /api/banner-list`

###  Health Score

18

—

LowBetter than 8% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity12

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity28

Early-stage or recently created project

 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.

### Community

Maintainers

![](https://www.gravatar.com/avatar/3680f83678f5410a92f3b6b3cd08275ac2eb7c06f8d819e3b6300451ee32c564?d=identicon)[Morais.Marcelo](/maintainers/Morais.Marcelo)

---

Top Contributors

[![moraismarcelo](https://avatars.githubusercontent.com/u/59709842?v=4)](https://github.com/moraismarcelo "moraismarcelo (9 commits)")

### Embed Badge

![Health badge](/badges/brediweb-banner/health.svg)

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

PHPackages © 2026

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