@atlaskit/editor-plugin-quick-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/button | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/modal-dialog | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/tmp-editor-statsig | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-metrics | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-analytics | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-type-ahead | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-connectivity | AI (dependencies): Same-org Atlassian package; expected dependency for an @atlaskit editor plugin. Not a security concern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org Atlassian package declared but not directly imported; minor code hygiene issue, not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes many packages without Sigstore provenance; publisher track record (147 approved, 0 rejected) provides sufficient trust signal. | ai |
Versions (showing 100 of 121)
| Version | Deps | Published |
|---|---|---|
| 11.0.1 | 13 / 6 | |
| 11.0.0 | 13 / 6 | |
| 10.4.10 | 13 / 6 | |
| 10.4.9 | 13 / 6 | |
| 10.4.8 | 13 / 6 | |
| 10.4.7 | 13 / 6 | |
| 10.4.6 | 13 / 6 | |
| 10.4.5 | 13 / 6 | |
| 10.4.4 | 13 / 6 | |
| 10.4.3 | 13 / 4 | |
| 10.4.2 | 13 / 4 | |
| 10.4.1 | 13 / 4 | |
| 10.4.0 | 13 / 4 | |
| 10.3.0 | 13 / 4 | |
| 10.2.11 | 13 / 4 | |
| 10.2.10 | 13 / 4 | |
| 10.2.9 | 13 / 4 | |
| 10.2.8 | 13 / 4 | |
| 10.2.7 | 13 / 4 | |
| 10.2.6 | 13 / 4 | |
| 10.2.5 | 13 / 4 | |
| 10.2.4 | 13 / 4 | |
| 10.2.3 | 13 / 4 | |
| 10.2.2 | 13 / 3 | |
| 10.2.1 | 13 / 3 | |
| 10.2.0 | 13 / 3 | |
| 10.1.4 | 13 / 3 | |
| 10.1.3 | 13 / 3 | |
| 10.1.2 | 13 / 3 | |
| 10.1.1 | 13 / 3 | |
| 10.1.0 | 13 / 3 | |
| 10.0.2 | 13 / 3 | |
| 10.0.1 | 13 / 3 | |
| 10.0.0 | 13 / 3 | |
| 9.0.0 | 13 / 2 | |
| 8.0.33 | 13 / 2 | |
| 8.0.32 | 13 / 2 | |
| 8.0.31 | 13 / 2 | |
| 8.0.30 | 13 / 2 | |
| 8.0.29 | 13 / 2 | |
| 8.0.28 | 13 / 2 | |
| 8.0.27 | 13 / 2 | |
| 8.0.26 | 13 / 2 | |
| 8.0.25 | 13 / 2 | |
| 8.0.24 | 13 / 2 | |
| 8.0.23 | 13 / 2 | |
| 8.0.22 | 13 / 2 | |
| 8.0.21 | 13 / 2 | |
| 8.0.20 | 13 / 2 | |
| 8.0.19 | 13 / 2 | |
| 8.0.18 | 13 / 2 | |
| 8.0.17 | 13 / 2 | |
| 8.0.16 | 13 / 2 | |
| 8.0.15 | 13 / 2 | |
| 8.0.14 | 13 / 2 | |
| 8.0.13 | 13 / 2 | |
| 8.0.12 | 13 / 2 | |
| 8.0.11 | 13 / 2 | |
| 8.0.10 | 14 / 2 | |
| 8.0.9 | 14 / 2 | |
| 8.0.8 | 14 / 2 | |
| 8.0.7 | 14 / 2 | |
| 8.0.6 | 14 / 2 | |
| 8.0.5 | 14 / 2 | |
| 8.0.4 | 14 / 2 | |
| 8.0.3 | 14 / 2 | |
| 8.0.2 | 14 / 2 | |
| 8.0.1 | 14 / 2 | |
| 8.0.0 | 14 / 2 | |
| 7.5.1 | 14 / 2 | |
| 7.5.0 | 14 / 2 | |
| 7.4.11 | 14 / 2 | |
| 7.4.10 | 14 / 2 | |
| 7.4.9 | 14 / 2 | |
| 7.4.8 | 14 / 2 | |
| 7.4.7 | 14 / 2 | |
| 7.4.6 | 14 / 2 | |
| 7.4.5 | 14 / 2 | |
| 7.4.4 | 14 / 2 | |
| 7.4.3 | 14 / 2 | |
| 7.4.2 | 14 / 2 | |
| 7.4.1 | 14 / 2 | |
| 7.4.0 | 14 / 2 | |
| 7.3.4 | 14 / 2 | |
| 7.3.3 | 14 / 2 | |
| 7.3.2 | 14 / 2 | |
| 7.3.1 | 14 / 2 | |
| 7.3.0 | 14 / 2 | |
| 7.2.2 | 14 / 2 | |
| 7.2.1 | 14 / 2 | |
| 7.2.0 | 14 / 2 | |
| 7.1.9 | 14 / 2 | |
| 7.1.8 | 14 / 2 | |
| 7.1.7 | 14 / 2 | |
| 7.1.6 | 14 / 2 | |
| 7.1.5 | 14 / 2 | |
| 7.1.4 | 14 / 2 | |
| 7.1.3 | 14 / 2 | |
| 7.1.2 | 14 / 2 | |
| 7.1.1 | 14 / 2 |
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.