@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a standard Atlaskit ecosystem alias for react-intl@^5.x, used consistently across all @atlaskit packages. Not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Atlaskit component packages routinely lack keywords and detailed READMEs on npm; they are internal enterprise components, not public-facing libraries requiring marketing content. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes via their artifact team pipeline without Sigstore provenance; this is consistent across all @atlaskit packages and not a security concern given the established publisher track record. | ai |
Versions (showing 100 of 179)
| Version | Deps | Published |
|---|---|---|
| 10.4.6 | 35 / 3 | |
| 10.4.5 | 35 / 3 | |
| 10.4.4 | 35 / 3 | |
| 10.4.3 | 35 / 3 | |
| 10.4.2 | 35 / 3 | |
| 10.4.1 | 35 / 3 | |
| 10.4.0 | 35 / 3 | |
| 10.3.9 | 35 / 3 | |
| 10.3.8 | 35 / 3 | |
| 10.3.7 | 35 / 3 | |
| 10.3.6 | 35 / 3 | |
| 10.3.5 | 35 / 3 | |
| 10.3.4 | 35 / 3 | |
| 10.3.3 | 35 / 3 | |
| 10.3.2 | 35 / 3 | |
| 10.3.1 | 35 / 3 | |
| 10.3.0 | 35 / 3 | |
| 10.2.16 | 35 / 3 | |
| 10.2.15 | 35 / 3 | |
| 10.2.14 | 35 / 3 | |
| 10.2.13 | 35 / 3 | |
| 10.2.12 | 35 / 3 | |
| 10.2.11 | 35 / 3 | |
| 10.2.10 | 35 / 3 | |
| 10.2.9 | 35 / 3 | |
| 10.2.8 | 35 / 3 | |
| 10.2.7 | 35 / 3 | |
| 10.2.6 | 35 / 3 | |
| 10.2.5 | 35 / 3 | |
| 10.2.4 | 35 / 3 | |
| 10.2.3 | 35 / 3 | |
| 10.2.2 | 34 / 3 | |
| 10.2.1 | 34 / 3 | |
| 10.2.0 | 34 / 3 | |
| 10.1.10 | 34 / 3 | |
| 10.1.9 | 34 / 3 | |
| 10.1.8 | 34 / 3 | |
| 10.1.7 | 34 / 3 | |
| 10.1.6 | 34 / 3 | |
| 10.1.5 | 34 / 3 | |
| 10.1.4 | 34 / 3 | |
| 10.1.3 | 34 / 3 | |
| 10.1.2 | 34 / 3 | |
| 10.1.1 | 34 / 3 | |
| 10.1.0 | 34 / 3 | |
| 10.0.21 | 34 / 3 | |
| 10.0.20 | 34 / 3 | |
| 10.0.19 | 34 / 3 | |
| 10.0.17 | 34 / 3 | |
| 10.0.16 | 34 / 3 | |
| 10.0.15 | 34 / 3 | |
| 10.0.14 | 34 / 3 | |
| 10.0.13 | 34 / 3 | |
| 10.0.12 | 34 / 3 | |
| 10.0.11 | 34 / 3 | |
| 10.0.10 | 34 / 3 | |
| 10.0.9 | 34 / 3 | |
| 10.0.8 | 34 / 3 | |
| 10.0.7 | 34 / 3 | |
| 10.0.6 | 34 / 3 | |
| 10.0.5 | 34 / 3 | |
| 10.0.4 | 34 / 3 | |
| 10.0.2 | 34 / 3 | |
| 10.0.1 | 34 / 3 | |
| 10.0.0 | 34 / 3 | |
| 9.1.21 | 34 / 3 | |
| 9.1.20 | 34 / 3 | |
| 9.1.19 | 34 / 3 | |
| 9.1.18 | 34 / 3 | |
| 9.1.17 | 34 / 3 | |
| 9.1.16 | 34 / 3 | |
| 9.1.15 | 34 / 3 | |
| 9.1.14 | 34 / 3 | |
| 9.1.11 | 34 / 3 | |
| 9.1.10 | 34 / 3 | |
| 9.1.9 | 34 / 3 | |
| 9.1.8 | 34 / 3 | |
| 9.1.7 | 34 / 3 | |
| 9.1.6 | 34 / 3 | |
| 9.1.4 | 34 / 3 | |
| 9.1.3 | 34 / 3 | |
| 9.1.2 | 34 / 3 | |
| 9.1.1 | 34 / 3 | |
| 9.1.0 | 34 / 3 | |
| 9.0.3 | 34 / 3 | |
| 9.0.2 | 34 / 3 | |
| 9.0.1 | 34 / 3 | |
| 9.0.0 | 34 / 3 | |
| 8.5.2 | 34 / 3 | |
| 8.5.1 | 34 / 3 | |
| 8.5.0 | 34 / 3 | |
| 8.4.14 | 34 / 3 | |
| 8.4.13 | 34 / 3 | |
| 8.4.12 | 34 / 3 | |
| 8.4.11 | 34 / 3 | |
| 8.4.10 | 34 / 3 | |
| 8.4.9 | 34 / 3 | |
| 8.4.8 | 34 / 3 | |
| 8.4.7 | 34 / 3 | |
| 8.4.6 | 34 / 3 |
v10.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.