@atlaskit/editor-plugin-media-insert
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/tmp-editor-statsig | AI (phantom-deps): Phantom dependency pattern is expected in Atlassian monorepo; declared for workspace consistency. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Phantom dependency pattern is expected in Atlassian monorepo; declared for workspace consistency. | ai | |
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a standard Atlassian npm alias pattern (npm:react-intl@^5.x) used consistently across the entire atlaskit ecosystem. Not a security risk. | ai | |
| phantom-deps | phantom-dep:@atlaskit/media-client | AI (phantom-deps): Phantom dep is within the same @atlaskit org scope; a minor code hygiene issue, not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes from their monorepo CI without Sigstore provenance; publisher track record (220 approved) provides sufficient trust signal. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 24.0.2 | 19 / 3 | |
| 24.0.1 | 19 / 3 | |
| 24.0.0 | 18 / 3 | |
| 23.3.2 | 18 / 1 | |
| 23.3.1 | 18 / 1 | |
| 23.3.0 | 18 / 1 | |
| 23.2.0 | 18 / 1 | |
| 23.1.0 | 18 / 1 | |
| 23.0.0 | 18 / 1 | |
| 22.0.0 | 19 / 0 | |
| 21.0.0 | 19 / 0 | |
| 20.0.2 | 19 / 0 | |
| 20.0.1 | 19 / 0 | |
| 20.0.0 | 19 / 0 | |
| 19.0.4 | 19 / 0 | |
| 19.0.3 | 19 / 0 | |
| 14.0.4 | 20 / 0 | |
| 14.0.2 | 20 / 0 | |
| 14.0.0 | 20 / 0 |
v24.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.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.
v21.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.
v20.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.
v20.0.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.
v20.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.
v19.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.
v19.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.
v14.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.
v14.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.
v14.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.