@atlaskit/editor-plugin-content-format
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 package within the same Atlaskit ecosystem; safe for all versions of this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a standard build-time convention in Atlaskit packages; declared as a dependency and loaded by the build framework. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 2 / 2 | |
| 4.1.0 | 2 / 1 | |
| 4.0.0 | 2 / 1 | |
| 3.0.0 | 2 / 1 | |
| 2.0.3 | 2 / 1 | |
| 2.0.2 | 2 / 1 | |
| 2.0.1 | 2 / 1 | |
| 2.0.0 | 2 / 1 | |
| 1.0.0 | 2 / 1 |
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.