@atlaskit/editor-plugin-insert-block
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/heading | AI (phantom-deps): Phantom deps are common in monorepo editor plugins; likely re-exported or used transitively through plugin architecture. | ai | |
| phantom-deps | phantom-dep:bind-event-listener | AI (phantom-deps): Declared in techstack config; used indirectly through plugin dependencies rather than direct import. | ai | |
| phantom-deps | phantom-dep:@atlaskit/primitives | AI (phantom-deps): Phantom deps are common in monorepo editor plugins; likely re-exported or used transitively through plugin architecture. | ai | |
| phantom-deps | phantom-dep:@atlaskit/button | AI (phantom-deps): Phantom deps are common in monorepo editor plugins; likely re-exported or used transitively through plugin architecture. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tooltip | AI (phantom-deps): Phantom deps are common in monorepo editor plugins; likely re-exported or used transitively through plugin architecture. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes via atlassianartifactteam with a strong track record (103 approved, 0 rejected); lack of Sigstore provenance is not a security risk in this context. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): @atlaskit/tokens is a same-org Atlassian design token package; phantom-dep finding is a packaging artifact, not a security concern for this package. | ai |
Versions (showing 33 of 151)
| Version | Deps | Published |
|---|---|---|
| 8.3.1 | 43 / 2 | |
| 8.3.0 | 43 / 2 | |
| 8.2.9 | 43 / 2 | |
| 8.2.8 | 43 / 2 | |
| 8.2.7 | 43 / 2 | |
| 8.2.6 | 43 / 2 | |
| 8.2.5 | 43 / 2 | |
| 8.2.4 | 43 / 2 | |
| 8.2.3 | 43 / 2 | |
| 8.2.2 | 43 / 2 | |
| 8.2.1 | 43 / 2 | |
| 8.2.0 | 43 / 2 | |
| 8.1.1 | 43 / 2 | |
| 8.1.0 | 43 / 2 | |
| 8.0.0 | 43 / 2 | |
| 7.2.0 | 43 / 2 | |
| 7.1.3 | 43 / 2 | |
| 7.1.2 | 43 / 2 | |
| 7.1.1 | 43 / 2 | |
| 7.1.0 | 43 / 2 | |
| 7.0.29 | 43 / 2 | |
| 7.0.28 | 43 / 2 | |
| 7.0.27 | 43 / 2 | |
| 7.0.26 | 43 / 2 | |
| 7.0.25 | 43 / 2 | |
| 7.0.24 | 43 / 2 | |
| 7.0.23 | 43 / 2 | |
| 7.0.22 | 47 / 5 | |
| 7.0.21 | 47 / 5 | |
| 7.0.20 | 47 / 5 | |
| 7.0.19 | 47 / 5 | |
| 7.0.18 | 47 / 5 | |
| 7.0.17 | 47 / 5 |
v8.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
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.2.0
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.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.