@grafana/runtime
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/index.d.cts | AI (source-diff): Bundled .d.cts type declarations, long lines from type unions, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/esm/index.d.mts | AI (source-diff): Bundled .d.mts type declarations, long lines from type unions, not obfuscated code. | ai | |
| phantom-deps | phantom-dep:@openfeature/web-sdk | AI (phantom-deps): Framework dep likely used via dynamic import/build config, not source-scannable. | ai | |
| phantom-deps | phantom-dep:@openfeature/ofrep-web-provider | AI (phantom-deps): Same OpenFeature provider pattern as other accepted phantom deps. | ai | |
| phantom-deps | phantom-dep:@types/systemjs | AI (phantom-deps): Type-only package loaded by convention; not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@openfeature/core | AI (phantom-deps): Transitive peer of @openfeature/react-sdk; referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; declared as dep, implicit usage is expected. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 13.1.1 | 18 / 17 | |
| 13.1.0 | 18 / 17 | |
| 13.0.3 | 16 / 20 | |
| 13.0.2 | 16 / 20 | |
| 13.0.1 | 16 / 20 | |
| 13.0.0 | 16 / 20 | |
| 12.4.6 | 15 / 20 | |
| 12.4.5 | 15 / 20 | |
| 12.4.4 | 15 / 20 | |
| 12.4.3 | 15 / 20 | |
| 12.4.2 | 15 / 20 | |
| 12.4.1 | 15 / 20 | |
| 12.4.0 | 15 / 20 | |
| 12.3.9 | 15 / 20 | |
| 12.3.8 | 15 / 20 | |
| 12.3.7 | 15 / 20 | |
| 12.3.6 | 15 / 20 | |
| 12.3.5 | 15 / 20 | |
| 12.3.4 | 15 / 20 | |
| 12.3.3 | 15 / 20 | |
| 12.3.2 | 15 / 20 | |
| 12.3.1 | 15 / 20 | |
| 12.3.0 | 15 / 20 | |
| 12.2.10 | 12 / 20 | |
| 12.2.9 | 12 / 20 | |
| 12.2.8 | 12 / 20 | |
| 12.2.7 | 12 / 20 | |
| 12.2.6 | 12 / 20 | |
| 12.2.5 | 12 / 20 | |
| 12.2.4 | 12 / 20 | |
| 12.2.3 | 12 / 20 | |
| 12.2.2 | 12 / 20 | |
| 12.2.1 | 12 / 20 | |
| 12.2.0 | 12 / 20 | |
| 12.1.10 | 12 / 21 | |
| 12.1.9 | 12 / 21 | |
| 12.1.8 | 12 / 21 | |
| 12.1.7 | 12 / 21 | |
| 12.1.6 | 12 / 21 | |
| 12.1.5 | 12 / 21 | |
| 12.1.4 | 12 / 21 | |
| 12.1.3 | 12 / 21 | |
| 12.1.2 | 12 / 21 | |
| 12.1.1 | 12 / 21 | |
| 12.1.0 | 12 / 21 | |
| 12.0.10 | 12 / 22 | |
| 12.0.9 | 12 / 22 | |
| 12.0.8 | 12 / 22 | |
| 12.0.5 | 12 / 22 | |
| 12.0.4 | 12 / 22 | |
| 12.0.3 | 12 / 22 |
v13.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.3.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.2.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.10
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.8
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.5
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (grafanabot) on 2025-09-24, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v12.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.