@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 21 of 139)
| Version | Deps | Published |
|---|---|---|
| 7.1.0 | 14 / 2 | |
| 7.0.1 | 14 / 2 | |
| 7.0.0 | 14 / 2 | |
| 6.2.0 | 14 / 2 | |
| 6.1.5 | 14 / 2 | |
| 6.1.4 | 14 / 2 | |
| 6.1.3 | 14 / 2 | |
| 6.1.2 | 14 / 2 | |
| 6.1.1 | 14 / 2 | |
| 6.1.0 | 14 / 2 | |
| 6.0.16 | 14 / 2 | |
| 6.0.15 | 14 / 2 | |
| 6.0.14 | 14 / 4 | |
| 6.0.13 | 14 / 4 | |
| 6.0.12 | 14 / 4 | |
| 6.0.11 | 14 / 4 | |
| 6.0.10 | 14 / 4 | |
| 6.0.9 | 14 / 4 | |
| 6.0.8 | 14 / 4 | |
| 6.0.7 | 13 / 4 | |
| 6.0.6 | 13 / 4 |
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.