@atlaskit/media-card
Includes all media card related components, CardView, CardViewSmall, Card...
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 | |
| 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/link | AI (phantom-deps): Same-org scoped phantom deps typical in Atlassian monorepo; no security impact. | ai | |
| phantom-deps | phantom-dep:@atlaskit/theme | AI (phantom-deps): Same-org scoped phantom deps typical in Atlassian monorepo; no security impact. | 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 108)
| Version | Deps | Published |
|---|---|---|
| 80.8.0 | 32 / 29 | |
| 80.7.5 | 31 / 29 | |
| 80.7.4 | 31 / 30 | |
| 80.7.3 | 31 / 30 | |
| 80.7.2 | 31 / 30 | |
| 80.7.1 | 31 / 30 | |
| 80.7.0 | 31 / 30 | |
| 80.6.1 | 31 / 30 | |
| 80.6.0 | 31 / 30 | |
| 80.5.9 | 31 / 30 | |
| 80.5.8 | 31 / 30 | |
| 80.5.7 | 31 / 30 | |
| 80.5.6 | 31 / 30 | |
| 80.5.5 | 31 / 30 | |
| 80.5.4 | 31 / 30 | |
| 80.5.3 | 31 / 30 | |
| 80.5.2 | 31 / 30 | |
| 80.5.1 | 31 / 30 | |
| 80.5.0 | 31 / 30 | |
| 80.4.11 | 31 / 30 | |
| 80.4.10 | 31 / 30 | |
| 80.4.9 | 31 / 30 | |
| 80.4.8 | 31 / 30 | |
| 80.4.7 | 31 / 30 | |
| 80.4.6 | 31 / 29 | |
| 80.4.5 | 31 / 29 | |
| 80.4.4 | 31 / 29 | |
| 80.4.3 | 31 / 29 | |
| 80.4.2 | 31 / 29 | |
| 80.4.1 | 31 / 29 | |
| 80.4.0 | 31 / 29 | |
| 80.3.4 | 32 / 29 | |
| 80.3.3 | 32 / 29 | |
| 80.3.2 | 32 / 29 | |
| 80.3.1 | 32 / 29 | |
| 80.3.0 | 32 / 29 | |
| 80.2.3 | 32 / 29 | |
| 80.2.2 | 32 / 29 | |
| 80.2.1 | 32 / 29 | |
| 80.2.0 | 32 / 29 | |
| 80.1.5 | 31 / 29 | |
| 80.1.4 | 31 / 29 | |
| 80.1.3 | 31 / 29 | |
| 80.1.2 | 31 / 29 | |
| 80.1.1 | 31 / 29 | |
| 80.1.0 | 31 / 29 | |
| 80.0.0 | 31 / 29 | |
| 79.16.23 | 31 / 29 | |
| 79.16.22 | 31 / 29 | |
| 79.16.21 | 31 / 29 | |
| 79.16.20 | 31 / 29 |
v80.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v80.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v80.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v80.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v80.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v80.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v79.16.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v79.16.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v79.16.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v79.16.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.