@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 27.0.10 | 18 / 3 | |
| 27.0.9 | 18 / 3 | |
| 27.0.8 | 18 / 3 | |
| 27.0.7 | 18 / 3 | |
| 27.0.6 | 18 / 3 | |
| 27.0.5 | 18 / 3 | |
| 27.0.4 | 18 / 3 | |
| 27.0.3 | 18 / 3 | |
| 27.0.2 | 18 / 3 | |
| 27.0.1 | 18 / 3 | |
| 27.0.0 | 18 / 3 | |
| 26.0.20 | 18 / 3 | |
| 26.0.19 | 18 / 3 | |
| 26.0.18 | 18 / 3 | |
| 26.0.17 | 18 / 3 | |
| 26.0.16 | 18 / 3 | |
| 26.0.15 | 18 / 3 | |
| 26.0.14 | 18 / 3 | |
| 26.0.13 | 18 / 3 | |
| 26.0.12 | 18 / 3 | |
| 26.0.11 | 18 / 3 | |
| 26.0.10 | 18 / 3 | |
| 26.0.9 | 18 / 3 | |
| 26.0.8 | 18 / 3 | |
| 26.0.7 | 18 / 3 | |
| 26.0.6 | 18 / 3 | |
| 26.0.5 | 18 / 3 | |
| 26.0.4 | 18 / 3 | |
| 26.0.3 | 18 / 3 | |
| 26.0.2 | 18 / 3 | |
| 26.0.1 | 19 / 3 | |
| 26.0.0 | 19 / 3 | |
| 25.0.8 | 19 / 3 | |
| 25.0.7 | 19 / 3 | |
| 25.0.6 | 19 / 3 | |
| 25.0.5 | 19 / 3 | |
| 25.0.4 | 19 / 3 | |
| 25.0.3 | 19 / 3 | |
| 25.0.2 | 18 / 3 | |
| 25.0.1 | 18 / 3 | |
| 25.0.0 | 18 / 3 | |
| 24.0.18 | 18 / 3 | |
| 24.0.17 | 19 / 3 | |
| 24.0.16 | 19 / 3 | |
| 24.0.15 | 19 / 3 | |
| 24.0.14 | 19 / 3 | |
| 24.0.13 | 19 / 3 | |
| 24.0.12 | 19 / 3 | |
| 24.0.9 | 19 / 3 | |
| 24.0.8 | 19 / 3 | |
| 24.0.7 | 19 / 3 |
v27.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.