@atlaskit/editor-ssr-renderer
SSR Renderer based on Editor
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 deps are all Atlassian-internal @atlaskit/* packages or well-known ecosystem packages (react-intl). Consistent with Atlassian monorepo refactoring patterns; no malicious signal. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian's atlassianartifactteam has a strong track record (2225 approved). Lack of Sigstore provenance is a low-risk gap for this established publisher. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a framework-scoped transitive dep commonly declared but not directly imported in Atlaskit monorepo packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-core | AI (dependencies): @atlaskit/editor-core is a first-party Atlaskit package from the same Atlassian org/publisher; unvetted status is a pipeline artifact, not a real risk. | ai | |
| phantom-deps | phantom-dep:@atlaskit/editor-prosemirror | AI (phantom-deps): Same org scope package; declared as a dependency for peer/transitive use in the Atlaskit editor stack, not a risk signal. | ai | |
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a standard Atlaskit ecosystem alias for react-intl@^5.18.1, a well-known i18n library. This aliasing pattern is consistent across all Atlaskit packages. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org @atlaskit scoped package declared but not directly imported; benign monorepo packaging pattern for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Atlaskit monorepo packages routinely have minimal READMEs and no keywords; this is a structural artifact of the monorepo, not a spam/low-value indicator. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 5 / 4 | |
| 6.0.0 | 5 / 4 | |
| 5.2.8 | 5 / 4 | |
| 5.2.7 | 5 / 4 | |
| 5.2.6 | 5 / 4 | |
| 5.2.5 | 5 / 4 | |
| 5.2.4 | 5 / 4 | |
| 5.2.3 | 5 / 3 | |
| 5.2.2 | 5 / 3 | |
| 5.2.1 | 5 / 3 | |
| 5.2.0 | 5 / 3 | |
| 5.1.15 | 5 / 3 | |
| 5.1.14 | 5 / 3 | |
| 5.1.13 | 5 / 3 | |
| 5.1.12 | 5 / 3 | |
| 5.1.11 | 5 / 3 | |
| 5.1.10 | 5 / 3 | |
| 5.1.9 | 5 / 3 | |
| 5.1.8 | 5 / 3 | |
| 5.1.7 | 5 / 2 | |
| 5.1.6 | 5 / 2 | |
| 5.1.5 | 5 / 2 | |
| 5.1.4 | 5 / 2 | |
| 5.1.3 | 5 / 2 | |
| 5.1.2 | 5 / 2 | |
| 5.1.1 | 5 / 2 | |
| 5.1.0 | 5 / 2 | |
| 5.0.3 | 5 / 2 | |
| 5.0.2 | 5 / 2 | |
| 5.0.1 | 5 / 1 | |
| 5.0.0 | 5 / 1 | |
| 4.0.0 | 6 / 0 | |
| 3.3.3 | 6 / 0 | |
| 3.3.2 | 6 / 0 | |
| 3.3.1 | 6 / 0 | |
| 3.2.3 | 6 / 0 | |
| 3.2.2 | 6 / 0 | |
| 3.2.0 | 6 / 0 | |
| 3.1.11 | 6 / 0 | |
| 3.1.9 | 6 / 0 | |
| 3.1.5 | 6 / 0 | |
| 3.1.3 | 6 / 0 | |
| 3.0.5 | 6 / 0 | |
| 2.2.2 | 6 / 0 | |
| 2.1.7 | 5 / 0 | |
| 1.2.0 | 5 / 0 | |
| 1.1.0 | 2 / 2 |
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.