PHPackages                             pinfirestudios/craft3-bugsnag - 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. [Logging & Monitoring](/categories/logging)
4. /
5. pinfirestudios/craft3-bugsnag

ActiveCraft-plugin[Logging & Monitoring](/categories/logging)

pinfirestudios/craft3-bugsnag
=============================

Enables errors to be sent to Bugsnag (www.bugsnag.com)

1.1.1(6y ago)47952MITPHPCI failing

Since Oct 31Pushed 6y ago1 watchersCompare

[ Source](https://github.com/pinfirestudios/craft3-bugsnag)[ Packagist](https://packagist.org/packages/pinfirestudios/craft3-bugsnag)[ RSS](/packages/pinfirestudios-craft3-bugsnag/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependencies (2)Versions (7)Used By (0)

Bugsnag plugin for Craft CMS 3.x
================================

[](#bugsnag-plugin-for-craft-cms-3x)

Enables errors to be sent to [Bugsnag](https://www.bugsnag.com)

Requirements
------------

[](#requirements)

This plugin requires Craft CMS 3.0.0-beta.23 or later.

Installation
------------

[](#installation)

To install the plugin, follow these instructions.

1. Open your terminal and go to your Craft project:

    `cd /path/to/project`
2. Then tell Composer to load the plugin:

    `composer require pinfirestudios/craft3-bugsnag`
3. In the Control Panel, go to Settings → Plugins and click the “Install” button for craft3-bugsnag.
4. If you want to be able to capture early initialization errors, you need to add this plugin to your project's [bootstrap configuration](http://www.yiiframework.com/doc-2.0/yii-base-application.html#$bootstrap-detail). To do this, in config/app.php, add:

    ```
    'bootstrap' => [
        '\pinfirestudios\craft3bugsnag\Bootstrap'
    ]

    ```

This will load the Bugsnag component and logging portion early in the project initialization, giving you the greatest visibility into errors. If you don't enable this, Bugsnag will be initialized when plugins are set up, later in the loading process.

Configuring craft3-bugsnag
--------------------------

[](#configuring-craft3-bugsnag)

You will need to provide your API key and optionally the release stage via the settings page or via config/env files. The recommended way however is to copy src/config.php to /APP\_ROOT/config/craft3-bugsnag.php, then either edit it directly, or add BUGSNAG\_API\_KEY to your .env file. For the release stage, if not set directly, it will default to the CRAFT\_ENVIRONMENT variable.

Using craft3-bugsnag
--------------------

[](#using-craft3-bugsnag)

If things crash and this is enabled, visit your Bugsnag dashboard to see why.

Getting JavaScript errors
-------------------------

[](#getting-javascript-errors)

If you would like to use Bugsnag's JavaScript on your site, you'll need to install *bower-asset/bugsnag*:

1. Add the following to your project's composer.json

    ```
    "repositories": [
        {
            "type": "composer",
            "url": "https://asset-packagist.org"
        }
    ]

    ```
2. Require bower-asset/bugsnag

    `composer require bower-asset/bugsnag`
3. Once you have it installed, add BugsnagAsset to your TWIG file (or controller if working inside a plugin)

In TWIG:

```
{% do view.registerAssetBundle("\\pinfirestudios\\yii2bugsnag\\BugsnagAsset") %}

```

In a plugin asset:

```
class AppAsset extends AssetBundle
{
    public $depends = [
        'pinfirestudios\yii2bugsnag\BugsnagAsset',
    ];
}

```

If you need to use version 2 of Bugsnag's JavaScript, you can specify the version in your configuration. See [Customizing Asset Bundles](http://www.yiiframework.com/doc-2.0/guide-structure-assets.html#customizing-asset-bundles).

###  Health Score

33

—

LowBetter than 75% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity19

Limited adoption so far

Community12

Small or concentrated contributor base

Maturity67

Established project with proven stability

 Bus Factor1

Top contributor holds 88.2% 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 ~170 days

Recently: every ~212 days

Total

6

Last Release

2264d ago

### Community

Maintainers

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

---

Top Contributors

[![jcherniak](https://avatars.githubusercontent.com/u/1727656?v=4)](https://github.com/jcherniak "jcherniak (15 commits)")[![brandonkelly](https://avatars.githubusercontent.com/u/47792?v=4)](https://github.com/brandonkelly "brandonkelly (1 commits)")[![zuccs](https://avatars.githubusercontent.com/u/1949725?v=4)](https://github.com/zuccs "zuccs (1 commits)")

---

Tags

cmsCraftcraftcmscraft-plugincraft3-bugsnag

### Embed Badge

![Health badge](/badges/pinfirestudios-craft3-bugsnag/health.svg)

```
[![Health](https://phpackages.com/badges/pinfirestudios-craft3-bugsnag/health.svg)](https://phpackages.com/packages/pinfirestudios-craft3-bugsnag)
```

###  Alternatives

[lukeyouell/craft-sentry

Error tracking that helps developers monitor and fix crashes in real time. Iterate continuously. Boost efficiency. Improve user experience.

17123.4k1](/packages/lukeyouell-craft-sentry)[superbig/craft-audit

Log adding/updating/deleting of elements

2053.6k](/packages/superbig-craft-audit)

PHPackages © 2026

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