@atlaskit/editor-plugin-loom
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): Official Atlassian design system package published by the same org; stable false positive for all @atlaskit/* packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/button | AI (dependencies): Official Atlassian design system package published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): Official Atlassian design system package published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@loomhq/record-sdk | AI (dependencies): Official Loom (Atlassian product) SDK; expected dependency for a Loom integration plugin. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-toolbar | AI (dependencies): Official Atlassian editor package published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): Official Atlassian editor package published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-width | AI (dependencies): Official Atlassian editor plugin published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-toolbar | AI (dependencies): Official Atlassian editor plugin published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): Official Atlassian platform package published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-analytics | AI (dependencies): Official Atlassian editor plugin published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-hyperlink | AI (dependencies): Official Atlassian editor plugin published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-connectivity | AI (dependencies): Official Atlassian editor plugin published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-quick-insert | AI (dependencies): Official Atlassian editor plugin published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-editor-viewmode | AI (dependencies): Official Atlassian editor plugin published by the same org; stable false positive. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-primary-toolbar | AI (dependencies): Official Atlassian editor plugin published by the same org; stable false positive. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same org scope; phantom dep pattern common in Atlassian monorepo packages where build-time vs runtime imports differ. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same org scope; phantom dep pattern common in Atlassian monorepo packages. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes many packages without Sigstore provenance; consistent with their publishing pipeline across 207+ approved packages. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 13.0.0 | 17 / 6 | |
| 12.1.1 | 17 / 4 | |
| 12.1.0 | 17 / 4 | |
| 12.0.0 | 17 / 4 | |
| 11.0.0 | 17 / 3 | |
| 10.0.9 | 17 / 3 | |
| 10.0.8 | 17 / 3 | |
| 10.0.7 | 17 / 3 | |
| 10.0.6 | 17 / 3 | |
| 10.0.5 | 17 / 3 | |
| 10.0.4 | 17 / 3 | |
| 10.0.3 | 17 / 3 | |
| 10.0.2 | 17 / 3 | |
| 10.0.1 | 17 / 3 | |
| 10.0.0 | 17 / 3 | |
| 9.3.4 | 17 / 3 | |
| 9.3.3 | 17 / 3 | |
| 9.3.2 | 16 / 3 | |
| 9.3.1 | 16 / 3 | |
| 9.3.0 | 16 / 3 | |
| 9.2.0 | 16 / 3 | |
| 9.1.2 | 16 / 3 | |
| 9.1.1 | 16 / 3 | |
| 9.1.0 | 16 / 3 | |
| 9.0.4 | 19 / 3 | |
| 9.0.3 | 19 / 3 | |
| 9.0.2 | 19 / 3 | |
| 9.0.1 | 19 / 3 | |
| 9.0.0 | 19 / 3 | |
| 8.1.0 | 19 / 3 | |
| 8.0.20 | 18 / 3 | |
| 8.0.19 | 18 / 3 | |
| 8.0.18 | 18 / 3 | |
| 8.0.17 | 18 / 3 | |
| 8.0.16 | 17 / 3 | |
| 8.0.15 | 17 / 3 | |
| 8.0.14 | 18 / 11 | |
| 8.0.13 | 18 / 11 | |
| 8.0.12 | 18 / 11 | |
| 8.0.11 | 18 / 11 |
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.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.
v10.0.3
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.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
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.1.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.