← Home

@grafana/api-clients

npm Repository Homepage

Grafana API client utilities

4
Versions
Apache-2.0
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

gf_joshhuntgrafanabot

Keywords

grafanatypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Grafana migrated publish to GitHub Actions CI; SLSA attestation confirms legitimate CI/CD origin. ai
provenance missing-githead AI (provenance): GitHub Actions publish environment change explains missing gitHead; SLSA provenance compensates. ai
source-diff large-new-source-files AI (source-diff): 193 new files are generated RTK-Query API client type definitions for a major version release. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Grafana's automated release pipeline uses 0.0.0 as a placeholder version; not indicative of malicious intent. ai

Versions (showing 4 of 4)

Version Deps Published
13.0.2 0 / 5
13.0.1 0 / 5
13.0.0 0 / 5
0.0.0 0 / 0

v13.0.2

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 Missing gitHead — previous versions had it provenance

[Accepted risk] 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.

v13.0.0

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

HIGH Publisher changed: grafanabot → GitHub Actions (on 2026-04-14) provenance

This version was published by a different npm account than previous versions on 2026-04-14. 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.0.0

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.