PHPackages                             emteknetnz/silverstripe-build-suffix - 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 & Helpers](/categories/utility)
4. /
5. emteknetnz/silverstripe-build-suffix

ActiveSilverstripe-module[Utility & Helpers](/categories/utility)

emteknetnz/silverstripe-build-suffix
====================================

Set file cache suffix to use the last dev/build timestamp

1.1.0(7y ago)21.9kBSD-3-ClausePHPPHP >=5.3.2

Since Sep 3Pushed 7y agoCompare

[ Source](https://github.com/emteknetnz/silverstripe-build-suffix)[ Packagist](https://packagist.org/packages/emteknetnz/silverstripe-build-suffix)[ RSS](/packages/emteknetnz-silverstripe-build-suffix/feed)WikiDiscussions master Synced yesterday

READMEChangelogDependencies (3)Versions (5)Used By (0)

Silverstripe Build Suffix
=========================

[](#silverstripe-build-suffix)

Introduction
------------

[](#introduction)

This module updates the ?m= suffix used js and css files by Requirements to a ?b= suffix that is the timestamp of the last dev/build.

The general idea is that front-end assets will be cached on a per-deployment basis, because dev/build is (or at least should be) run as part of the deployment process.

If your deployment process does not include a dev/build, then you probably should not use this module.

Usage
-----

[](#usage)

Just install the module and the suffix will be automatically used on test and live environments.

Dev environments will continue to use the default ?m= suffix so that newly built front end assets don't get stuck in a browser cache.

You can change this behaviour for different environments by updating config.yml in your mysite folder, e.g.

BuiltAtRequirementsBackend: use\_backend\_dev: true

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

[](#requirements)

SilverStripe 3

There is currently no SilverStripe 4 version of this module

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

[](#installation)

composer require emteknetnz/silverstripe-build-suffix:^1

###  Health Score

29

—

LowBetter than 60% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity18

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity60

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

Total

4

Last Release

2801d ago

### Community

Maintainers

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

---

Top Contributors

[![emteknetnz](https://avatars.githubusercontent.com/u/4809037?v=4)](https://github.com/emteknetnz "emteknetnz (12 commits)")

---

Tags

silverstripe

### Embed Badge

![Health badge](/badges/emteknetnz-silverstripe-build-suffix/health.svg)

```
[![Health](https://phpackages.com/badges/emteknetnz-silverstripe-build-suffix/health.svg)](https://phpackages.com/packages/emteknetnz-silverstripe-build-suffix)
```

PHPackages © 2026

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