@atlaskit/editor-plugin-base
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:@atlaskit/adf-schema | AI (dependencies): Internal Atlaskit monorepo dependency published by the same Atlassian organization; unvetted status is a systemic artifact, not a real risk signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): Internal Atlaskit monorepo dependency published by the same Atlassian organization; unvetted status is a systemic artifact, not a real risk signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/tmp-editor-statsig | AI (dependencies): Internal Atlaskit monorepo dependency published by the same Atlassian organization; unvetted status is a systemic artifact, not a real risk signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/prosemirror-history | AI (dependencies): Internal Atlaskit monorepo dependency published by the same Atlassian organization; unvetted status is a systemic artifact, not a real risk signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/feature-gate-js-client | AI (dependencies): Internal Atlaskit monorepo dependency published by the same Atlassian organization; unvetted status is a systemic artifact, not a real risk signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-feature-flags | AI (dependencies): Internal Atlaskit monorepo dependency published by the same Atlassian organization; unvetted status is a systemic artifact, not a real risk signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-context-identifier | AI (dependencies): Internal Atlaskit monorepo dependency published by the same Atlassian organization; unvetted status is a systemic artifact, not a real risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes the entire @atlaskit monorepo without Sigstore provenance; this is a consistent pattern across all their packages and not a risk indicator. | ai |
Versions (showing 51 of 141)
| Version | Deps | Published |
|---|---|---|
| 13.0.32 | 8 / 0 | |
| 13.0.31 | 8 / 0 | |
| 13.0.30 | 8 / 0 | |
| 13.0.29 | 8 / 0 | |
| 13.0.28 | 8 / 0 | |
| 13.0.27 | 8 / 0 | |
| 13.0.26 | 8 / 0 | |
| 13.0.25 | 8 / 0 | |
| 13.0.24 | 8 / 0 | |
| 13.0.23 | 8 / 0 | |
| 13.0.22 | 8 / 0 | |
| 13.0.21 | 8 / 0 | |
| 13.0.20 | 8 / 0 | |
| 13.0.19 | 8 / 0 | |
| 13.0.18 | 8 / 0 | |
| 13.0.17 | 8 / 0 | |
| 13.0.16 | 8 / 0 | |
| 13.0.15 | 8 / 0 | |
| 13.0.14 | 8 / 0 | |
| 13.0.13 | 8 / 0 | |
| 13.0.12 | 8 / 0 | |
| 13.0.11 | 8 / 0 | |
| 13.0.10 | 8 / 0 | |
| 13.0.9 | 8 / 0 | |
| 13.0.8 | 8 / 0 | |
| 13.0.7 | 8 / 0 | |
| 13.0.6 | 8 / 0 | |
| 13.0.5 | 8 / 0 | |
| 13.0.4 | 8 / 0 | |
| 13.0.3 | 8 / 0 | |
| 13.0.2 | 8 / 0 | |
| 13.0.1 | 8 / 0 | |
| 13.0.0 | 8 / 0 | |
| 12.1.14 | 8 / 0 | |
| 12.1.13 | 8 / 0 | |
| 12.1.12 | 8 / 0 | |
| 12.1.11 | 8 / 0 | |
| 12.1.10 | 8 / 0 | |
| 12.1.9 | 8 / 0 | |
| 12.1.6 | 8 / 0 | |
| 12.1.5 | 8 / 0 | |
| 12.1.4 | 8 / 0 | |
| 12.1.3 | 8 / 0 | |
| 12.1.2 | 8 / 0 | |
| 12.1.1 | 8 / 0 | |
| 12.1.0 | 8 / 0 | |
| 12.0.2 | 8 / 0 | |
| 12.0.1 | 8 / 0 | |
| 12.0.0 | 8 / 0 | |
| 11.1.8 | 8 / 0 | |
| 11.1.7 | 8 / 0 |
v13.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.