← Home

@grafana/experimental

npm Repository Homepage
9
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ivanahuckovabmateidomasx2clordiwysiuleventebaloghandresmgotortorkelodprokoppeteholmbergryantxumcknsunkergrafanabottolzhabayevdsotirakisscottleppgrafanajwestbrookacademo_grafanareemtariqqyulia.shanyrovateodosiibrojd-grafana

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Gap is an artifact of diffing against an old imported version, not real dormancy on npm. ai
publish-pattern new-deps-added AI (publish-pattern): Well-known libraries added by official Grafana maintainers, not a supply-chain risk. ai
phantom-deps phantom-dep:@types/uuid AI (phantom-deps): Types package used by convention, not a real risk. ai

Versions (showing 9 of 9)

Version Deps Published
2.1.6 8 / 38
2.1.5 8 / 38
2.1.4 8 / 38
2.1.3 8 / 38
2.1.2 8 / 38
2.1.1 8 / 38
2.1.0 8 / 38
2.0.0 8 / 38
1.7.4 3 / 34

v2.1.6

1 finding
LOW No provenance attestation provenance

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

v2.1.5

1 finding
LOW No provenance attestation provenance

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

v2.1.4

1 finding
LOW No provenance attestation provenance

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.7.4

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.