← Home

@canonical/react-ds-global-form

Form components for the Pragma design system. This package provides a field system built on react-hook-form with two core patterns: a field switch for rendering different input types and middleware composition for extending field behavior.

21
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 from manual to CI/CD publish (GitHub Actions + SLSA attestation) is a provenance improvement, not a takeover signal. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of human publisher is expected when package moves to automated CI/CD publishing pipeline. ai
phantom-deps phantom-dep:@canonical/styles AI (phantom-deps): Same-org package; phantom-dep heuristic is a false positive for this monorepo structure. ai
phantom-deps phantom-dep:@canonical/storybook-config AI (phantom-deps): Same-org storybook config; used in config files, not directly imported in source. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): react-dom is a peer/runtime dep referenced in config; phantom-dep is a false positive here. ai

Versions (showing 21 of 21)

Version Deps Published
0.32.0 8 / 27
0.31.0 8 / 27
0.30.0 8 / 27
0.29.1 8 / 26
0.29.0 8 / 26
0.28.0 8 / 26
0.27.0 8 / 26
0.26.0 8 / 27
0.25.0 8 / 27
0.24.0 8 / 27
0.23.0 8 / 27
0.22.0 8 / 27
0.21.0 8 / 27
0.20.0 8 / 26
0.17.1 8 / 24
0.17.0 8 / 24
0.16.0 8 / 24
0.15.1 8 / 24
0.15.0 8 / 24
0.11.0 8 / 20
0.10.0 8 / 19

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.1

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.22.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-04-03, known maintainer) provenance

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

v0.21.0

1 finding
LOW No provenance attestation provenance

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

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.