@atlaskit/editor-plugin-media-editing
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a standard npm alias for react-intl@^5.x, widely used across Atlassian packages. Not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Atlassian monorepo packages commonly lack standalone README code blocks and keywords; documentation is maintained in the monorepo. Not indicative of spam or malice. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): First-party Atlassian package from the same org scope; not a security concern. | ai | |
| dependencies | unvetted-dep:cropperjs | AI (dependencies): cropperjs is a well-known image cropping library; its use in a media editing plugin is expected and legitimate. | ai | |
| dependencies | unvetted-dep:@atlaskit/css | AI (dependencies): First-party Atlassian package from the same org scope; not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): First-party Atlassian package from the same org scope; not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/button | AI (dependencies): First-party Atlassian package from the same org scope; not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party Atlassian package from the same org scope; not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/modal-dialog | AI (dependencies): First-party Atlassian package from the same org scope; not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/dropdown-menu | AI (dependencies): First-party Atlassian package from the same org scope; not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): First-party Atlassian package from the same org scope; not a security concern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/css | AI (phantom-deps): Same org scope as this package; phantom dep is a minor packaging concern, not a security issue. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes many packages without Sigstore provenance; this is consistent across their ecosystem and not a security disqualifier. | ai | |
| dependencies | unvetted-dep:@atlaskit/media-client | AI (dependencies): First-party Atlassian package from the same org scope; not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/spinner | AI (dependencies): First-party Atlassian package from the same org scope; not a security concern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 14 / 3 | |
| 4.1.1 | 14 / 2 | |
| 4.1.0 | 14 / 2 | |
| 4.0.1 | 14 / 2 | |
| 4.0.0 | 14 / 2 | |
| 2.0.5 | 15 / 1 | |
| 2.0.4 | 15 / 1 | |
| 2.0.3 | 15 / 1 | |
| 2.0.2 | 15 / 1 | |
| 1.0.0 | 7 / 1 | |
| 0.1.0 | 7 / 1 |
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.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.
v1.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.
v0.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.