← Home

@atlaskit/media-svg

npm Repository Homepage
26
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): Same-org Atlassian config-only dep; not imported at runtime, stable false positive for this package. ai
phantom-deps phantom-dep:@atlaskit/link AI (phantom-deps): Phantom dep within the same @atlaskit org scope; common in Atlassian monorepo packages where deps may be used in test helpers or transitively. Not a security concern. ai
provenance no-provenance AI (provenance): Atlassian publishes @atlaskit packages without Sigstore provenance; this is consistent across their entire package ecosystem and not a security risk for this publisher. ai

Versions (showing 26 of 26)

Version Deps Published
3.1.0 8 / 16
3.0.1 8 / 16
3.0.0 7 / 17
2.3.1 7 / 16
2.3.0 7 / 15
2.2.2 7 / 15
2.2.1 7 / 15
2.2.0 8 / 15
2.1.14 8 / 15
2.1.13 8 / 14
2.1.12 9 / 14
2.1.11 9 / 14
2.1.10 9 / 14
2.1.9 9 / 14
2.1.8 9 / 14
2.1.7 9 / 14
2.1.6 9 / 14
2.1.5 9 / 16
2.1.4 9 / 16
2.1.3 9 / 16
2.1.2 9 / 16
2.1.1 9 / 16
2.1.0 9 / 16
2.0.2 8 / 16
2.0.1 8 / 16
2.0.0 8 / 16

v2.0.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.

v2.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.