← Home

@canonical/renovate-config

Shared Renovate configuration for Canonical monorepos. Provides batching families, weekly schedule, and devDep automerge.

14
Versions
GPL-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 from manual to GitHub Actions CI/CD publish; matches IMPROVED provenance direction and SLSA attestation. ai
maintainer-change maintainer-removed AI (maintainer-change): mariadias143 removed as part of legitimate migration to GitHub Actions publishing for this Canonical org package. ai

Versions (showing 14 of 14)

Version Deps Published
0.32.0 0 / 1
0.31.0 0 / 1
0.30.0 0 / 1
0.29.0 0 / 0
0.28.0 0 / 0
0.27.0 0 / 0
0.26.0 0 / 0
0.25.0 0 / 0
0.24.0 0 / 0
0.23.0 0 / 0
0.22.0 0 / 0
0.21.0 0 / 0
0.20.0 0 / 0
0.17.1 0 / 0

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: ad.vl → mariadias143 (on 2026-03-26, known maintainer) provenance

This version was published by a different npm account (mariadias143) than the most recent previously approved version (ad.vl) on 2026-03-26, but mariadias143 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.