@atlaskit/media-document-viewer
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:@atlaskit/css | AI (phantom-deps): First-party Atlaskit CSS package; phantom dep pattern is expected in compiled CSS design system components from Atlassian monorepo. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): First-party Atlaskit design tokens package; phantom dep pattern is expected in Atlassian design system components using compiled CSS. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.7.2 | 8 / 9 | |
| 0.7.1 | 8 / 9 | |
| 0.7.0 | 8 / 8 | |
| 0.6.11 | 8 / 8 | |
| 0.6.10 | 9 / 8 | |
| 0.6.9 | 9 / 8 | |
| 0.6.8 | 9 / 8 | |
| 0.6.7 | 9 / 8 | |
| 0.6.6 | 10 / 8 | |
| 0.6.5 | 10 / 7 | |
| 0.6.4 | 10 / 7 | |
| 0.6.3 | 10 / 7 | |
| 0.6.2 | 10 / 7 | |
| 0.6.1 | 10 / 7 | |
| 0.6.0 | 10 / 7 | |
| 0.5.3 | 10 / 7 | |
| 0.5.2 | 10 / 7 | |
| 0.5.1 | 10 / 7 | |
| 0.5.0 | 10 / 7 | |
| 0.4.4 | 9 / 6 | |
| 0.4.3 | 9 / 6 | |
| 0.4.2 | 9 / 6 | |
| 0.4.1 | 9 / 6 | |
| 0.4.0 | 9 / 6 | |
| 0.3.8 | 9 / 6 | |
| 0.3.7 | 9 / 6 | |
| 0.3.6 | 9 / 6 | |
| 0.3.5 | 9 / 7 | |
| 0.3.4 | 9 / 8 | |
| 0.3.3 | 9 / 8 | |
| 0.3.2 | 9 / 8 | |
| 0.3.1 | 8 / 8 | |
| 0.3.0 | 7 / 7 | |
| 0.2.3 | 7 / 7 | |
| 0.2.2 | 7 / 7 | |
| 0.2.1 | 6 / 7 | |
| 0.2.0 | 6 / 7 | |
| 0.1.0 | 5 / 7 |
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.