← Home

@n8n/design-system

![n8n.io - Workflow Automation](https://user-images.githubusercontent.com/65276001/173571060-9f2f6d7b-bac0-43b6-bdb2-001da9694058.png)

51
Versions
SEE LICENSE IN LICENSE.md
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

cornelius_n8n_ion8n-matsuuutomin8njan_n8n_ion8n-charliekolb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/compact-Q0gG5s1Q.js AI (source-diff): File is a bundled emojibase-data JSON dataset; long lines are emoji unicode records, not obfuscation. ai
maintainer-change maintainer-removed AI (maintainer-change): n8n migrated to GitHub Actions CI publishing; maintainer list change is consistent with org-wide automation transition. ai
source-diff obfuscated-file:dist/compact-CWM3h4JV.js AI (source-diff): File is a minified JSON blob of emoji unicode data — no obfuscation or malicious payload. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are n8n org accounts; consistent with org-level team management. ai
provenance publisher-changed AI (provenance): tomin8n is an n8n org account with 10 approved packages and SLSA provenance; publisher rotation is expected for this org. ai
source-diff encoded-string-file:dist/n8n-design-system.es.js AI (source-diff): Encoded string is UMALQURA_DATA Islamic calendar lookup table, a known benign base64 blob from date library dependencies. ai
publish-pattern dormant-publish AI (publish-pattern): Established n8n org package with SLSA provenance; dormancy reflects release cadence, not account takeover. ai

Versions (showing 51 of 69)

View all versions
Version Deps Published
2.31.0 0 / 0
2.30.2 0 / 0
2.30.1 0 / 0
2.30.0 0 / 0
2.29.1 0 / 0
2.29.0 0 / 0
2.28.3 0 / 0
2.28.2 0 / 0
2.28.1 0 / 0
2.28.0 0 / 0
2.27.2 0 / 0
2.27.1 0 / 0
2.27.0 0 / 0
2.26.0 0 / 0
2.25.0 0 / 0
2.24.2 0 / 0
2.24.1 0 / 0
2.24.0 0 / 0
2.23.0 0 / 0
2.22.0 0 / 0
2.21.0 0 / 0
2.20.1 0 / 0
2.20.0 0 / 0
2.19.0 0 / 0
2.18.2 0 / 0
2.18.1 0 / 0
2.18.0 0 / 0
2.17.1 0 / 0
2.17.0 0 / 0
2.16.0 0 / 0
2.15.0 0 / 0
2.14.0 0 / 0
2.13.2 0 / 0
2.13.1 0 / 0
2.13.0 0 / 0
2.12.0 0 / 0
2.11.2 0 / 0
2.11.1 0 / 0
2.11.0 0 / 0
2.10.1 0 / 0
2.10.0 0 / 0
2.9.3 0 / 0
2.9.2 0 / 0
2.9.1 0 / 0
2.9.0 0 / 0
2.8.0 0 / 0
2.7.1 0 / 0
2.7.0 0 / 0
2.6.1 0 / 0
2.6.0 0 / 0
2.5.0 0 / 0

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

v2.30.2

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.

v2.30.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.

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

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

v2.29.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.

v2.28.3

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.

v2.28.2

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.

v2.28.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.

v2.28.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.

v2.27.2

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.

v2.14.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.

v2.13.2

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.

v2.13.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.

v2.13.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.

v2.12.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.

v2.11.2

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.

v2.11.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.

v2.11.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.

v2.10.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.

v2.10.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.

v2.9.3

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.

v2.9.2

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.

v2.9.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.

v2.9.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.

v2.8.0

2 findings
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.

INFO Publisher changed: tomin8n → GitHub Actions (on 2026-02-10) provenance

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