@atlaskit/editor-synced-block-provider
Synced Block Provider for @atlaskit/editor-plugin-synced-block
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 Atlassian dependency; common in monorepo packages where deps are re-exported or used transitively. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org Atlassian dependency; common in monorepo packages where deps are re-exported or used transitively. | ai | |
| phantom-deps | phantom-dep:@atlaskit/primitives | AI (phantom-deps): Same-org Atlassian dependency; common in monorepo packages where deps are re-exported or used transitively. | ai | |
| dependencies | unvetted-dep:@atlaskit/node-data-provider | AI (dependencies): First-party Atlaskit dependency from the same trusted Atlassian publisher. Expected internal dependency. | ai | |
| dependencies | unvetted-dep:@atlaskit/tmp-editor-statsig | AI (dependencies): First-party Atlaskit dependency from the same trusted Atlassian publisher. Expected internal dependency. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party Atlaskit dependency from the same trusted Atlassian publisher. Expected internal dependency. | ai | |
| dependencies | unvetted-dep:@compiled/react | AI (dependencies): @compiled/react is Atlassian's own CSS-in-JS library, a standard dependency across the Atlaskit ecosystem. Not a security risk. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Phantom dep in config files only; common pattern in Atlaskit monorepo build tooling. Not a security concern. | ai | |
| phantom-deps | phantom-dep:@compiled/react | AI (phantom-deps): Phantom dep in config files only; @compiled/react is Atlassian's own library referenced in build config. Not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-json-transformer | AI (dependencies): First-party Atlaskit dependency from the same trusted Atlassian publisher. Expected internal dependency. | ai | |
| dependencies | unvetted-dep:@atlaskit/adf-utils | AI (dependencies): First-party Atlaskit dependency from the same trusted Atlassian publisher. Expected internal dependency. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): First-party Atlaskit dependency from the same trusted Atlassian publisher. Expected internal dependency. | ai |
Versions (showing 51 of 199)
| Version | Deps | Published |
|---|---|---|
| 7.0.1 | 12 / 3 | |
| 7.0.0 | 12 / 3 | |
| 6.7.2 | 12 / 3 | |
| 6.7.1 | 12 / 3 | |
| 6.7.0 | 12 / 3 | |
| 6.6.12 | 12 / 3 | |
| 6.6.11 | 12 / 3 | |
| 6.6.10 | 12 / 3 | |
| 6.6.9 | 12 / 3 | |
| 6.6.8 | 12 / 3 | |
| 6.6.7 | 12 / 2 | |
| 6.6.6 | 12 / 2 | |
| 6.6.5 | 12 / 2 | |
| 6.6.4 | 12 / 2 | |
| 6.6.3 | 12 / 2 | |
| 6.6.2 | 12 / 2 | |
| 6.6.1 | 12 / 2 | |
| 6.6.0 | 12 / 2 | |
| 6.5.3 | 12 / 2 | |
| 6.5.2 | 12 / 2 | |
| 6.5.1 | 12 / 2 | |
| 6.5.0 | 12 / 2 | |
| 6.4.3 | 12 / 2 | |
| 6.4.2 | 12 / 2 | |
| 6.4.1 | 12 / 2 | |
| 6.4.0 | 12 / 2 | |
| 6.3.2 | 12 / 2 | |
| 6.3.1 | 12 / 2 | |
| 6.3.0 | 12 / 2 | |
| 6.2.6 | 12 / 2 | |
| 6.2.5 | 12 / 2 | |
| 6.2.4 | 12 / 2 | |
| 6.2.3 | 12 / 2 | |
| 6.2.2 | 12 / 2 | |
| 6.2.1 | 12 / 2 | |
| 6.2.0 | 12 / 2 | |
| 6.1.4 | 12 / 2 | |
| 6.1.3 | 12 / 2 | |
| 6.1.2 | 12 / 2 | |
| 6.1.1 | 12 / 2 | |
| 6.1.0 | 12 / 2 | |
| 6.0.0 | 12 / 2 | |
| 5.0.0 | 12 / 2 | |
| 4.5.4 | 12 / 2 | |
| 4.5.3 | 12 / 2 | |
| 4.5.2 | 12 / 2 | |
| 4.5.1 | 12 / 2 | |
| 4.5.0 | 12 / 2 | |
| 4.4.3 | 12 / 2 | |
| 4.4.2 | 12 / 2 | |
| 4.4.1 | 12 / 2 |
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.