@atlaskit/editor-plugin-engagement-platform
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/editor-prosemirror | AI (dependencies): @atlaskit/editor-prosemirror is an internal Atlassian monorepo package published by the same trusted publisher; unvetted status is a registry artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-analytics | AI (dependencies): @atlaskit/editor-plugin-analytics is an internal Atlassian monorepo package published by the same trusted publisher; unvetted status is a registry artifact, not a real risk. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian's atlaskit packages consistently lack Sigstore provenance; publisher track record (282 approved) provides sufficient trust signal. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 12.0.0 | 3 / 2 | |
| 11.0.0 | 3 / 0 | |
| 10.0.0 | 3 / 0 | |
| 9.0.3 | 3 / 0 | |
| 9.0.2 | 3 / 0 | |
| 9.0.1 | 3 / 0 | |
| 9.0.0 | 3 / 0 | |
| 8.0.0 | 3 / 0 |
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.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.