@atlaskit/editor-presets
Public editor presets for Atlassian Editor containing base configurations for Confluence and other products
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is from same @atlassian org scope; consistent with this package's established pattern of adding Atlassian editor plugins. | ai | |
| phantom-deps | phantom-dep:@atlaskit/adf-schema | AI (phantom-deps): Same-org @atlaskit scope package; phantom dep finding is a low-risk artifact of the Atlaskit monorepo build process. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes @atlaskit packages without Sigstore provenance; this is consistent across the entire @atlaskit ecosystem and not a security concern. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.2.3 | 98 / 1 | |
| 3.2.1 | 98 / 1 | |
| 3.2.0 | 98 / 1 | |
| 3.1.2 | 98 / 1 | |
| 3.1.0 | 98 / 1 | |
| 3.0.1 | 97 / 1 | |
| 3.0.0 | 97 / 1 | |
| 2.1.1 | 97 / 1 | |
| 2.1.0 | 97 / 1 | |
| 2.0.13 | 97 / 1 | |
| 2.0.12 | 97 / 1 | |
| 2.0.11 | 97 / 1 | |
| 2.0.10 | 97 / 1 | |
| 2.0.9 | 97 / 1 | |
| 2.0.8 | 97 / 1 | |
| 2.0.7 | 97 / 1 | |
| 2.0.6 | 97 / 1 | |
| 2.0.5 | 97 / 1 | |
| 2.0.4 | 97 / 1 | |
| 2.0.3 | 97 / 1 | |
| 2.0.2 | 97 / 1 | |
| 2.0.1 | 97 / 1 | |
| 2.0.0 | 97 / 1 | |
| 1.0.0 | 97 / 0 | |
| 0.2.3 | 97 / 0 | |
| 0.2.2 | 97 / 0 | |
| 0.2.1 | 97 / 0 | |
| 0.2.0 | 97 / 0 | |
| 0.1.5 | 97 / 0 | |
| 0.1.4 | 97 / 0 | |
| 0.1.3 | 98 / 0 | |
| 0.1.2 | 98 / 0 | |
| 0.1.1 | 98 / 0 | |
| 0.1.0 | 98 / 0 |
v3.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.