← Home

@grafana/components

npm Repository Homepage

Product Design Engineering Components for Grafana

15
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

gf_joshhuntgrafanabot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Grafana's CI pipeline change explains missing gitHead; consistent with other build script changes in this version. ai
publish-pattern new-deps-added AI (publish-pattern): clsx is a well-established, widely-used utility; no malicious history or supply chain risk. ai
phantom-deps phantom-dep:clsx AI (phantom-deps): clsx is a well-known utility; phantom-dep fires because it's referenced in config/build files rather than directly imported in source. ai
dependencies unvetted-dep:@grafana/data AI (dependencies): First-party Grafana package; stable dependency for this Grafana component library. ai
dependencies unvetted-dep:@grafana/design-tokens AI (dependencies): First-party Grafana design system package; expected dependency for this library. ai
dependencies unvetted-dep:react-useportal AI (dependencies): Well-known React portal utility; low risk for a UI component library. ai
source-diff large-new-source-files AI (source-diff): Size increase driven by icon asset files (iconMetaData.js, allIcons.js) added in this version; expected for a component library. ai
source-diff source-size-tripled AI (source-diff): Growth attributable to icon data assets and rollup build output; not injected payload. ai
phantom-deps phantom-dep:@grafana/data AI (phantom-deps): Same-org @grafana/data; declared as peer/dep in a component library, phantom-dep heuristic is a stable false positive here. ai
provenance no-provenance AI (provenance): Grafana org package published via grafanabot; provenance absence is common and not a risk signal here. ai
phantom-deps phantom-dep:@emotion/react AI (phantom-deps): @emotion/react is a declared runtime dep used in build/config context; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:react-useportal AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package. ai

Versions (showing 15 of 15)

Version Deps Published
0.3.0 8 / 28
0.0.63 6 / 61
0.0.60 6 / 61
0.0.33 9 / 49
0.0.24 8 / 50
0.0.22 8 / 50
0.0.17 8 / 50
0.0.15 8 / 50
0.0.10 7 / 42
0.0.9 7 / 42
0.0.8 7 / 42
0.0.6 7 / 42
0.0.5 7 / 41
0.0.4 7 / 41
0.0.3 7 / 41

v0.3.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO No provenance attestation provenance

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

v0.0.60

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

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

INFO No provenance attestation provenance

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

v0.0.33

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.15

1 finding
INFO No provenance attestation provenance

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

v0.0.10

1 finding
INFO No provenance attestation provenance

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

v0.0.9

1 finding
INFO No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding
INFO No provenance attestation provenance

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

v0.0.4

1 finding
INFO No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.