@atlaskit/editor-plugin-panel
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/ui/renderPanelIcon.js | AI (source-diff): Long lines are SVG path data strings for panel icons, not obfuscated code. This is a standard pattern in Atlaskit UI packages. | ai | |
| source-diff | obfuscated-file:dist/esm/ui/renderPanelIcon.js | AI (source-diff): Long lines are SVG path data strings for panel icons, not obfuscated code. ESM variant of the same legitimate pattern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/emoji | AI (phantom-deps): Same-org Atlaskit dependency declared in package.json; used transitively or conditionally in this monorepo package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org Atlaskit dependency declared in package.json; used transitively or conditionally in this monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes the entire @atlaskit monorepo without Sigstore provenance; this is a stable publishing pattern for this org, not a security concern. | ai |
Versions (showing 24 of 144)
| Version | Deps | Published |
|---|---|---|
| 9.0.4 | 19 / 0 | |
| 9.0.3 | 19 / 0 | |
| 9.0.2 | 19 / 0 | |
| 9.0.0 | 19 / 0 | |
| 8.2.4 | 19 / 0 | |
| 8.2.3 | 19 / 0 | |
| 8.2.2 | 19 / 0 | |
| 8.2.1 | 19 / 0 | |
| 8.2.0 | 19 / 0 | |
| 8.1.19 | 19 / 0 | |
| 8.1.18 | 19 / 0 | |
| 8.1.17 | 19 / 0 | |
| 8.1.16 | 19 / 0 | |
| 8.1.15 | 19 / 0 | |
| 8.1.14 | 19 / 0 | |
| 8.1.13 | 19 / 0 | |
| 8.1.12 | 19 / 0 | |
| 8.1.11 | 19 / 0 | |
| 8.1.10 | 19 / 0 | |
| 8.1.9 | 19 / 0 | |
| 8.1.8 | 19 / 0 | |
| 8.1.7 | 19 / 0 | |
| 8.1.6 | 19 / 0 | |
| 8.1.5 | 19 / 0 |
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.0
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.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.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.
v8.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.