← Home

@atlaskit/media-picker

38
Versions
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@atlassian/react-compiler-gating AI (phantom-deps): Atlassian-namespaced tooling/config dep; declared but not directly imported, consistent with build tooling use. ai
provenance no-provenance AI (provenance): Atlassian publishes via atlassianartifactteam with a strong track record; lack of Sigstore provenance is consistent across their entire package portfolio and is not a risk signal here. ai

Versions (showing 38 of 38)

Version Deps Published
72.1.3 16 / 22
72.1.2 16 / 22
72.1.1 16 / 22
72.1.0 16 / 22
72.0.2 16 / 22
72.0.1 15 / 23
72.0.0 15 / 23
71.4.0 15 / 24
71.3.1 15 / 24
71.3.0 15 / 24
71.2.2 15 / 23
71.2.1 15 / 23
71.2.0 15 / 22
71.1.0 16 / 23
71.0.1 16 / 23
71.0.0 16 / 23
70.1.19 16 / 23
70.1.18 16 / 23
70.1.17 16 / 23
70.1.16 16 / 23
70.1.15 16 / 23
70.1.14 17 / 23
70.1.13 17 / 23
70.1.12 17 / 23
70.1.11 17 / 23
70.1.10 17 / 23
70.1.9 17 / 23
70.1.8 17 / 23
70.1.7 17 / 23
70.1.6 17 / 23
70.1.5 17 / 23
70.1.4 17 / 23
70.1.3 17 / 23
70.1.2 17 / 23
70.1.1 17 / 23
70.1.0 17 / 23
70.0.9 17 / 23
70.0.8 17 / 23

v72.1.3

1 finding
INFO No provenance attestation provenance

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

v72.1.2

1 finding
INFO No provenance attestation provenance

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

v72.1.1

1 finding
INFO No provenance attestation provenance

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