@atlaskit/editor-toolbar-model No license 87 versions

@atlaskit/editor-toolbar-model

npm Repository Homepage

87

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@compiled/react	AI (dependencies): @compiled/react is Atlassian's own CSS-in-JS build tool, a standard dependency across the @atlaskit ecosystem.	ai	2026/04/24
dependencies	unvetted-dep:@atlaskit/tokens	AI (dependencies): @atlaskit/tokens is Atlassian's design token package, a standard dependency across all @atlaskit UI components.	ai	2026/04/24
dependencies	unvetted-dep:@atlaskit/tmp-editor-statsig	AI (dependencies): Internal Atlaskit editor feature-flagging package, expected dependency for @atlaskit editor components.	ai	2026/04/24
phantom-deps	phantom-dep:@compiled/react	AI (phantom-deps): @compiled/react is a build-time CSS-in-JS tool; config-only reference without direct import is the expected usage pattern.	ai	2026/04/24
phantom-deps	phantom-dep:@atlaskit/tokens	AI (phantom-deps): @atlaskit/tokens is same-org and commonly declared without direct import in Atlaskit packages that use it transitively.	ai	2026/04/24

Versions (showing 87 of 87)

Version	Deps	Published
0.5.9	4 / 5	2026/06/04
0.5.8	4 / 5	2026/06/02
0.5.7	4 / 5	2026-06-02
0.5.6	4 / 5	2026-06-01
0.5.5	4 / 5	2026-05-28
0.5.4	4 / 5	2026-05-26
0.5.3	4 / 5	2026-05-25
0.5.2	4 / 4	2026-05-21
0.5.1	4 / 4	2026-05-18
0.5.0	4 / 4	2026-05-15
0.4.54	4 / 4	2026-05-13
0.4.53	4 / 4	2026-05-13
0.4.52	4 / 4	2026-05-12
0.4.51	4 / 4	2026-05-07
0.4.50	4 / 4	2026-05-07
0.4.49	4 / 4	2026-05-06
0.4.48	4 / 4	2026-05-01
0.4.47	4 / 4	2026-04-30
0.4.46	4 / 4	2026-04-29
0.4.45	4 / 4	2026-04-28
0.4.44	4 / 4	2026-04-27
0.4.43	4 / 4	2026-04-24
0.4.42	4 / 4	2026-04-24
0.4.41	4 / 4	2026-04-24
0.4.40	4 / 4	2026-04-23
0.4.39	4 / 4	2026-04-23
0.4.38	4 / 4	2026-04-22
0.4.37	4 / 4	2026-04-21
0.4.36	4 / 3	2026-04-20
0.4.35	4 / 3	2026-04-15
0.4.34	4 / 3	2026-04-14
0.4.33	4 / 3	2026-04-14
0.4.32	4 / 3	2026-04-14
0.4.31	4 / 3	2026-04-13
0.4.30	4 / 3	2026-04-13
0.4.29	4 / 3	2026-04-13
0.4.28	4 / 3	2026-04-10
0.4.27	4 / 3	2026-04-10
0.4.26	4 / 3	2026-04-09
0.4.25	4 / 3	2026-04-02
0.4.24	4 / 3	2026-04-02
0.4.23	4 / 3	2026-04-01
0.4.22	4 / 3	2026-03-31
0.4.21	4 / 3	2026-03-31
0.4.20	4 / 3	2026-03-30
0.4.19	4 / 3	2026-03-27
0.4.18	4 / 3	2026-03-26
0.4.17	4 / 3	2026-03-25
0.4.16	4 / 3	2026-03-25
0.4.15	4 / 3	2026-03-24
0.4.14	4 / 3	2026-03-23
0.4.13	4 / 3	2026-03-23
0.4.12	4 / 3	2026-03-23
0.4.11	4 / 3	2026-03-18
0.4.10	4 / 3	2026-03-18
0.4.9	4 / 3	2026-03-17
0.4.8	4 / 3	2026-03-17
0.4.7	4 / 3	2026-03-16
0.4.6	4 / 3	2026-03-10
0.4.5	4 / 3	2026-03-07
0.4.4	4 / 3	2026-03-06
0.4.3	4 / 3	2026-02-27
0.4.2	4 / 3	2026-02-26
0.4.1	4 / 3	2026-02-26
0.4.0	4 / 3	2026-02-24
0.3.2	3 / 3	2026-02-02
0.3.1	3 / 3	2026-01-22
0.3.0	4 / 3	2026-01-16
0.2.11	4 / 3	2025-12-18
0.2.10	4 / 3	2025-12-17
0.2.9	4 / 3	2025-12-08
0.2.8	6 / 6	2025-11-24
0.2.7	6 / 6	2025-11-20
0.2.6	6 / 6	2025-11-07
0.2.5	6 / 6	2025-10-16
0.2.4	6 / 6	2025-10-15
0.2.3	6 / 6	2025-10-13
0.2.2	5 / 6	2025-09-05
0.2.1	5 / 6	2025-09-04
0.2.0	5 / 6	2025-08-29
0.1.2	5 / 6	2025-08-25
0.1.1	5 / 7	2025-08-15
0.1.0	5 / 7	2025-08-11
0.0.4	5 / 7	2025-08-06
0.0.3	5 / 8	2025-08-04
0.0.2	5 / 8	2025-08-04
0.0.1	5 / 8	2025-08-01

v0.5.9

1 finding

LOW No provenance attestation provenance

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

v0.5.8

1 finding

LOW No provenance attestation provenance

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

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.54

1 finding

LOW No provenance attestation provenance

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

v0.4.53

1 finding

LOW No provenance attestation provenance

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

v0.4.52

1 finding

LOW No provenance attestation provenance

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

v0.4.51

1 finding

LOW No provenance attestation provenance

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

v0.4.50

1 finding

LOW No provenance attestation provenance

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

v0.4.49

1 finding

LOW No provenance attestation provenance

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

v0.4.48

1 finding

LOW No provenance attestation provenance

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

v0.4.47

1 finding

LOW No provenance attestation provenance

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

v0.4.44

1 finding

LOW No provenance attestation provenance

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

v0.4.43

1 finding

LOW No provenance attestation provenance

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

v0.4.42

1 finding

LOW No provenance attestation provenance

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

v0.4.41

1 finding

LOW No provenance attestation provenance

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

v0.4.40

1 finding

LOW No provenance attestation provenance

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

v0.4.39

1 finding

LOW No provenance attestation provenance

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

v0.4.38

1 finding

LOW No provenance attestation provenance

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

v0.4.37

1 finding

LOW No provenance attestation provenance

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

v0.4.36

1 finding

LOW No provenance attestation provenance

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

v0.4.35

1 finding

LOW No provenance attestation provenance

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

v0.4.34

1 finding

LOW No provenance attestation provenance

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

v0.4.33

1 finding

LOW No provenance attestation provenance

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

v0.4.32

1 finding

LOW No provenance attestation provenance

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

v0.4.31

1 finding

LOW No provenance attestation provenance

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

v0.4.30

1 finding

LOW No provenance attestation provenance

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

v0.4.29

1 finding

LOW No provenance attestation provenance

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

v0.4.28

1 finding

LOW No provenance attestation provenance

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

v0.4.27

1 finding

LOW No provenance attestation provenance

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

v0.4.26

1 finding

LOW No provenance attestation provenance

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

v0.4.25

1 finding

LOW No provenance attestation provenance

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

v0.4.24

1 finding

LOW No provenance attestation provenance

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

v0.4.23

1 finding

LOW No provenance attestation provenance

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

v0.4.22

1 finding

LOW No provenance attestation provenance

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

v0.4.21

1 finding

LOW No provenance attestation provenance

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

v0.4.20

1 finding

LOW No provenance attestation provenance

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

v0.4.19

1 finding

LOW No provenance attestation provenance

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

v0.4.18

1 finding

LOW No provenance attestation provenance

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

v0.4.17

1 finding

LOW No provenance attestation provenance

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

v0.4.16

1 finding

LOW No provenance attestation provenance

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

v0.4.15

1 finding

LOW No provenance attestation provenance

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

v0.4.14

1 finding

LOW No provenance attestation provenance

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

v0.4.13

1 finding

LOW No provenance attestation provenance

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

v0.4.12

1 finding

LOW No provenance attestation provenance

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

v0.4.11

1 finding

LOW No provenance attestation provenance

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

v0.4.10

1 finding

LOW No provenance attestation provenance

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

v0.4.9

1 finding

LOW No provenance attestation provenance

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

v0.4.8

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.11

1 finding

LOW No provenance attestation provenance

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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