← Home

@atlaskit/editor-json-transformer

100
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change reflects Atlassian's migration to atlassianartifactteam; stable for this package family. ai
provenance missing-githead AI (provenance): Changed publish environment due to org migration; no malicious signal given the publisher's track record. ai
maintainer-change maintainer-takeover AI (maintainer-change): Atlassian org restructure; atlaskit-user confirmed as known maintainer by email match on prior approved versions. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are Atlassian org accounts; legitimate org-level publisher migration. ai
maintainer-change maintainer-removed AI (maintainer-change): Old atlaskit account replaced by org accounts; consistent with Atlassian's known migration pattern. ai
dependencies unvetted-dep:@atlaskit/adf-schema AI (dependencies): @atlaskit/adf-schema is a first-party Atlassian package, expected dependency for this editor transformer. ai
dependencies unvetted-dep:@atlaskit/adf-utils AI (dependencies): @atlaskit/adf-utils is a first-party Atlassian package, expected dependency for this editor transformer. ai
dependencies unvetted-dep:@atlaskit/editor-prosemirror AI (dependencies): @atlaskit/editor-prosemirror is a first-party Atlassian package, expected dependency for this editor transformer. ai
provenance no-provenance AI (provenance): Atlassian's atlassianartifactteam publisher has 98 approved packages; lack of provenance is consistent across their entire catalog and not a meaningful risk signal for this established package. ai

Versions (showing 100 of 142)

Version Deps Published
9.1.0 5 / 3
9.0.2 5 / 3
9.0.1 5 / 3
9.0.0 5 / 3
8.33.2 5 / 3
8.33.1 5 / 3
8.33.0 5 / 3
8.32.0 5 / 3
8.31.8 5 / 2
8.31.7 5 / 2
8.31.6 5 / 2
8.31.5 5 / 2
8.31.4 5 / 1
8.31.3 5 / 1
8.31.2 5 / 1
8.31.1 5 / 1
8.31.0 5 / 1
8.30.0 5 / 1
8.29.1 5 / 1
8.29.0 5 / 1
8.28.0 5 / 1
8.27.2 5 / 1
8.27.1 5 / 1
8.27.0 5 / 1
8.26.1 5 / 1
8.26.0 5 / 1
8.25.1 5 / 2
8.25.0 5 / 2
8.24.5 5 / 2
8.24.4 5 / 2
8.24.3 5 / 2
8.24.2 6 / 2
8.24.1 6 / 2
8.24.0 6 / 2
8.23.1 6 / 3
8.23.0 6 / 3
8.22.2 6 / 3
8.22.1 6 / 3
8.22.0 6 / 3
8.21.2 6 / 3
8.21.1 6 / 3
8.21.0 6 / 3
8.20.4 5 / 4
8.20.3 5 / 4
8.20.2 5 / 4
8.20.1 5 / 4
8.20.0 5 / 4
8.19.1 5 / 4
8.19.0 5 / 4
8.18.2 5 / 4
8.18.1 5 / 3
8.18.0 5 / 4
8.17.0 5 / 4
8.16.0 5 / 4
8.15.1 5 / 4
8.15.0 5 / 4
8.14.0 5 / 4
8.13.2 5 / 4
8.13.1 5 / 4
8.13.0 5 / 4
8.12.1 5 / 4
8.12.0 5 / 4
8.11.5 5 / 3
8.11.4 5 / 3
8.11.3 5 / 3
8.11.2 5 / 3
8.11.1 5 / 3
8.11.0 5 / 3
8.10.33 5 / 3
8.10.32 5 / 3
8.10.31 5 / 3
8.10.30 5 / 3
8.10.29 5 / 3
8.10.28 5 / 3
8.10.27 5 / 3
8.10.26 5 / 3
8.10.25 5 / 3
8.10.24 5 / 3
8.10.23 5 / 3
8.10.22 5 / 3
8.10.21 5 / 3
8.10.20 5 / 3
8.10.19 5 / 3
8.10.18 5 / 3
8.10.17 5 / 3
8.10.16 5 / 3
8.10.15 5 / 3
8.10.14 5 / 3
8.10.13 5 / 3
8.10.12 5 / 3
8.10.11 4 / 4
8.10.10 4 / 4
8.10.9 4 / 4
8.10.8 4 / 5
8.10.7 4 / 5
8.10.6 4 / 5
8.10.5 4 / 5
8.10.4 4 / 5
8.10.3 4 / 5
8.10.2 4 / 9
Showing 100 of 142 Next page →

v9.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.10.32

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.31

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.30

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.29

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.28

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.27

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.25

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.24

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.23

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.20

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.19

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.18

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.17

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.16

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.15

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.14

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.13

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.11

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.10.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.