PHPackages                             balsama/lightning\_strict - 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. [Utility &amp; Helpers](/categories/utility)
4. /
5. balsama/lightning\_strict

AbandonedArchivedMetapackage[Utility &amp; Helpers](/categories/utility)

balsama/lightning\_strict
=========================

Locked Composer dependencies for Lightning Drupal distribution releases.

4.1.5(6y ago)13.0kGPL-2.0+PHPPHP &gt;=7.0

Since Jan 18Pushed 6y ago1 watchersCompare

[ Source](https://github.com/balsama/lightning_strict)[ Packagist](https://packagist.org/packages/balsama/lightning_strict)[ RSS](/packages/balsama-lightning-strict/feed)WikiDiscussions master Synced yesterday

READMEChangelogDependencies (227)Versions (163)Used By (0)

Lightning Strict
================

[](#lightning-strict)

This package will lock all of the dependencies defined by Lightning to the specific versions that were used in testing each Lightning release.

Usage
-----

[](#usage)

```
composer require acquia/lightning:VERSION balsama/lightning_strict:VERSION --no-update
composer update

```

`VERSION` is the specific version of Lightning you want to build. For example, `2.2.4`, or `3.0.1`. It should be the same for both the `acquia/lightning` and the `balsama/lightning_strict` packagesYou might need to run `composer update`more than once for the composer-patches plugin to properly patch all dependencies.

Motivation
----------

[](#motivation)

Lightning 2.2.0 required `drupal/core:~8.4.0` which translates roughly to:

> "Give me the most recent version of core lower than 8.5.0"

At the time of this writing, that would be `8.4.4`. But when Lightning 2.2.0 was tagged on 4 October 2017, `8.4.0` was the most recent version of drupal/core. So that tag was actually tested against 8.4.0. This is true for all dependencies of Lightning - and any project that uses Composer to manage its dependencies.

When using Composer, it's usually best to let your dependencies manage their own constraints. To allow the highest amount of flexibility and fewest conflicts, Lightning is intentionally lenient (where it can be) when constraining dependencies.

However, under certain circumstances, it might be necessary to build a specific version of Lightning with dependencies exactly as they were when it was released. For example, you might need an update path that was removed from Lightning long ago, but building the version might be problematic because a dependency is no longer available, or a patch no longer applies. In that case, you can use this package to pin all of Lightning's dependencies (and their dependencies recursively) to the specific versions included in Lightning's composer.lock file when it was released.

PHP Version
-----------

[](#php-version)

Lightning's dependencies are updated in an environment which runs php 7.0. Since this package is directly based on historical Lightning composer.lock files, that means that certain dependencies will need at least php 7.0 to run. We've added a minimum PHP version to the generated composer.json files. Unfortunately, there is no workaround if your environment uses PHP 5.6.

Inspiration
-----------

[](#inspiration)

This was inspired by and heavily borrows code from [webflo's](https://github.com/webflo)awesome [drupal-core-strict project](https://github.com/webflo/drupal-core-strict). Thank you.

###  Health Score

35

—

LowBetter than 77% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity18

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity77

Established project with proven stability

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

Recently: every ~0 days

Total

81

Last Release

2204d ago

Major Versions

3.2.7 → 4.0.02019-05-20

3.3.4 → 4.0.12019-08-01

3.4.1 → 4.1.12020-01-15

3.4.2 → 4.1.22020-06-17

3.4.3 → 4.1.32020-06-17

### Community

Maintainers

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

---

Top Contributors

[![balsama](https://avatars.githubusercontent.com/u/1536654?v=4)](https://github.com/balsama "balsama (8 commits)")

###  Code Quality

TestsPHPUnit

Code StylePHP\_CodeSniffer

### Embed Badge

![Health badge](/badges/balsama-lightning-strict/health.svg)

```
[![Health](https://phpackages.com/badges/balsama-lightning-strict/health.svg)](https://phpackages.com/packages/balsama-lightning-strict)
```

###  Alternatives

[drupal/core-recommended

Locked core dependencies; require this project INSTEAD OF drupal/core.

6941.5M396](/packages/drupal-core-recommended)[drupal/core

Drupal is an open source content management platform powering millions of websites and applications.

19664.8M1.6k](/packages/drupal-core)[shopware/core

Shopware platform is the core for all Shopware ecommerce products.

585.4M524](/packages/shopware-core)[sylius/sylius

E-Commerce platform for PHP, based on Symfony framework.

8.5k5.8M712](/packages/sylius-sylius)[sulu/sulu

Core framework that implements the functionality of the Sulu content management system

1.3k1.4M196](/packages/sulu-sulu)[oro/platform

Business Application Platform (BAP)

642140.7k104](/packages/oro-platform)

PHPackages © 2026

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