← Home

@canonical/biome-config

This is a [Biome](https://biomejs.dev/) configuration that provides a set of default configurations for Biome projects.

23
Versions
LGPL-3.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ilayda21frankbanhuwshimianthonydillonsteverydzamylily1011bartazjpmartinsptpetesfrenchjmuzinamtrujedlerdabehniacanonical-organizationedisile-canonicalsteciuk-canonicalad.vlengr-aliando.gqninfa_jeonndv99goulin-canonicalimmortalcodesalvaromateoonibenjo-canonical

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI/CD publishing is an improvement; matches canonical org repo with SLSA attestation. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of personal account reflects migration to automated CI/CD publishing under the canonical org. ai

Versions (showing 23 of 23)

Version Deps Published
0.32.0 0 / 1
0.31.0 0 / 1
0.30.0 0 / 1
0.29.0 0 / 1
0.28.0 0 / 1
0.27.0 0 / 1
0.26.0 0 / 1
0.25.0 0 / 1
0.24.0 0 / 1
0.23.0 0 / 1
0.22.0 0 / 1
0.21.0 0 / 1
0.20.0 0 / 1
0.17.1 0 / 1
0.17.0 0 / 1
0.16.0 0 / 1
0.15.0 0 / 1
0.14.0 0 / 1
0.13.0 0 / 1
0.12.0 0 / 1
0.11.0 0 / 1
0.10.0 0 / 1
0.9.0 0 / 1

v0.32.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.31.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.30.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.29.0

2 findings
HIGH Publisher changed: mariadias143 → GitHub Actions (on 2026-07-03) provenance

This version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.20.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jmuzina → mariadias143 (on 2026-03-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.

v0.17.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jmuzina → ad.vl (on 2026-03-04, known maintainer) provenance

This version was published by a different npm account (ad.vl) than the most recent previously approved version (jmuzina) on 2026-03-04, but ad.vl is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.16.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jmuzina → ad.vl (on 2026-03-03, known maintainer) provenance

This version was published by a different npm account (ad.vl) than the most recent previously approved version (jmuzina) on 2026-03-03, but ad.vl is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.