@atlaskit/editor-plugin-alignment
Alignment plugin for @atlaskit/editor-core
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/css | AI (phantom-deps): Same-org @atlaskit/css declared but not directly imported; common in Atlassian monorepo packages where build tooling handles usage. Not a security concern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org @atlaskit/tokens declared but not directly imported; common in Atlassian monorepo packages. Not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Established Atlassian package published by atlassianartifactteam with 35 approved packages. Lack of provenance is common and not a risk signal here. | ai |
Versions (showing 7 of 125)
| Version | Deps | Published |
|---|---|---|
| 7.1.10 | 15 / 3 | |
| 7.1.9 | 15 / 7 | |
| 7.1.8 | 15 / 7 | |
| 7.1.7 | 15 / 7 | |
| 7.1.6 | 15 / 7 | |
| 7.1.5 | 15 / 7 | |
| 7.1.4 | 15 / 7 |
v7.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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.
v7.1.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.