← Home

@atlaskit/media-card

npm Repository Homepage

Includes all media card related components, CardView, CardViewSmall, Card...

51
Versions
Apache-2.0
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:@atlaskit/progress-bar AI (phantom-deps): Same org scope (@atlaskit); phantom dep pattern is consistent with this monorepo package. ai
phantom-deps phantom-dep:@atlassian/react-compiler-gating AI (phantom-deps): Config-only reference within the same Atlassian org scope; not directly imported at runtime. ai
phantom-deps phantom-dep:classnames AI (phantom-deps): Phantom deps in monorepo packages are common; declared but unused deps don't affect runtime security. ai
phantom-deps phantom-dep:eventemitter2 AI (phantom-deps): Phantom deps in monorepo packages are common; declared but unused deps don't affect runtime security. ai
phantom-deps phantom-dep:@atlaskit/theme AI (phantom-deps): Same-org scoped phantom deps typical in Atlassian monorepo; no security impact. ai
phantom-deps phantom-dep:@atlaskit/link AI (phantom-deps): Same-org scoped phantom deps typical in Atlassian monorepo; no security impact. ai
phantom-deps phantom-dep:lru_map AI (phantom-deps): Phantom deps in monorepo packages are common; declared but unused deps don't affect runtime security. ai
provenance no-provenance AI (provenance): Atlassian publishes this package via their artifact pipeline without Sigstore provenance; this is consistent across all their releases and not a security concern for this trusted publisher. ai

Versions (showing 51 of 161)

View all versions
Version Deps Published
81.4.16 33 / 28
81.4.15 33 / 28
81.4.14 33 / 28
81.4.13 33 / 28
81.4.12 33 / 28
81.4.11 33 / 28
81.4.10 33 / 28
81.4.9 33 / 28
81.4.8 33 / 28
81.4.7 33 / 28
81.4.6 33 / 28
81.4.5 33 / 28
81.4.4 33 / 28
81.4.3 33 / 28
81.4.2 33 / 28
81.4.1 33 / 28
81.4.0 33 / 28
81.3.4 33 / 28
81.3.3 33 / 28
81.3.2 33 / 28
81.3.1 33 / 28
81.3.0 33 / 28
81.2.6 33 / 28
81.2.5 33 / 28
81.2.4 33 / 28
81.2.3 33 / 28
81.2.2 33 / 28
81.2.1 33 / 28
81.2.0 33 / 28
81.1.6 33 / 28
81.1.5 33 / 28
81.1.4 33 / 28
81.1.3 33 / 28
81.1.2 33 / 28
81.1.1 32 / 29
81.1.0 32 / 29
81.0.4 32 / 29
81.0.3 32 / 29
81.0.2 32 / 29
81.0.1 32 / 29
81.0.0 32 / 29
80.8.14 32 / 29
80.8.13 32 / 29
80.8.12 32 / 29
80.8.11 32 / 29
80.8.10 32 / 29
80.8.9 32 / 29
80.8.6 32 / 29
80.8.5 32 / 29
80.8.4 32 / 29
80.8.3 32 / 29

v81.4.16

1 finding
INFO No provenance attestation provenance

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

v81.4.15

1 finding
INFO No provenance attestation provenance

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

v81.4.14

1 finding
INFO No provenance attestation provenance

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

v81.4.13

1 finding
INFO No provenance attestation provenance

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

v81.4.12

1 finding
INFO No provenance attestation provenance

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

v81.4.11

1 finding
INFO No provenance attestation provenance

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

v81.4.10

1 finding
INFO No provenance attestation provenance

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

v81.4.9

1 finding
INFO No provenance attestation provenance

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

v81.4.8

1 finding
INFO No provenance attestation provenance

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

v81.4.7

1 finding
INFO No provenance attestation provenance

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

v81.4.6

1 finding
INFO No provenance attestation provenance

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

v81.4.5

1 finding
INFO No provenance attestation provenance

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

v81.4.4

1 finding
INFO No provenance attestation provenance

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

v81.4.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.

v81.4.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.

v81.4.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.

v81.4.0

1 finding
INFO No provenance attestation provenance

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

v81.3.4

1 finding
INFO No provenance attestation provenance

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

v81.3.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.

v81.3.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.

v81.3.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.

v81.3.0

1 finding
INFO No provenance attestation provenance

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

v81.2.6

1 finding
INFO No provenance attestation provenance

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

v81.2.5

1 finding
INFO No provenance attestation provenance

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

v81.2.4

1 finding
INFO No provenance attestation provenance

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

v81.2.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.

v81.2.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.

v81.2.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.