@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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; declared as dep, implicit usage is expected. | 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 |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 13.0.2 | 16 / 20 | |
| 12.4.4 | 15 / 20 | |
| 12.4.2 | 15 / 20 | |
| 12.3.7 | 15 / 20 | |
| 12.2.9 | 12 / 20 | |
| 12.1.6 | 12 / 21 | |
| 12.0.2 | 12 / 22 | |
| 12.0.1 | 12 / 22 | |
| 12.0.0 | 12 / 22 | |
| 11.6.10 | 11 / 24 |
v13.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.4.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.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.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.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.