@graphql-tools/delegate

A set of utils for faster development of GraphQL tools

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

dotansimhaurigoardatanenisdenjotheguild-bot

Versions (showing 100 of 571)

Hide prereleases

Version	Deps	Published
12.0.16	8 / 3	2026-05-07
12.0.15	8 / 3	2026-05-01
12.0.14	8 / 3	2026-04-15
12.0.13	8 / 3	2026-04-03
12.0.12	8 / 3	2026-03-17
12.0.11	8 / 3	2026-03-16
12.0.10	8 / 3	2026-03-15
12.0.9	8 / 3	2026-03-10
12.0.6	8 / 3	2026-02-04
12.0.3	8 / 3	2026-01-07
12.0.2	8 / 3	2025-12-03
11.1.3	8 / 3	2025-11-19
11.1.2	8 / 3	2025-11-07
11.1.1	9 / 3	2025-11-01
11.1.0	9 / 3	2025-10-27
11.0.0	9 / 3	2025-09-04
10.2.23	9 / 3	2025-08-01
10.2.22	9 / 3	2025-07-23
10.2.20	9 / 3	2025-06-26
10.2.19	9 / 3	2025-06-02
10.2.18	9 / 3	2025-05-16
10.2.14	9 / 3	2025-03-11
10.2.12	8 / 2	2025-02-13
10.2.11	8 / 2	2025-01-29
10.2.9	8 / 2	2024-12-24
10.2.8	8 / 2	2024-12-13
10.2.6	8 / 2	2024-12-04
10.2.5	8 / 2	2024-12-03
10.2.3	8 / 2	2024-12-02
10.2.2	8 / 2	2024-11-29
10.2.1	8 / 2	2024-11-27
10.1.3	8 / 2	2024-11-19
10.1.2	8 / 0	2024-11-13
10.1.1	8 / 0	2024-11-01
10.1.0	8 / 0	2024-10-31
10.0.29	8 / 0	2024-10-31
10.0.28	8 / 0	2024-10-30
10.0.27	7 / 0	2024-10-24
10.0.26	7 / 0	2024-10-17
10.0.25	7 / 0	2024-10-16
10.0.24	7 / 0	2024-10-16
10.0.23	7 / 0	2024-10-16
10.0.22	7 / 0	2024-10-15
10.0.21	7 / 0	2024-08-26
10.0.20	7 / 0	2024-08-26
10.0.19	7 / 0	2024-08-14
10.0.18	7 / 0	2024-08-07
10.0.17	6 / 0	2024-08-01
10.0.16	6 / 0	2024-07-23
10.0.15	6 / 0	2024-07-22
10.0.14	6 / 0	2024-07-18
10.0.13	6 / 0	2024-07-03
10.0.12	6 / 0	2024-07-01
10.0.11	6 / 0	2024-05-27
10.0.10	6 / 0	2024-05-08
10.0.9	6 / 0	2024-05-02
10.0.8	6 / 0	2024-05-02
10.0.7	6 / 0	2024-04-29
10.0.6	6 / 0	2024-04-26
10.0.5	6 / 0	2024-04-26
10.0.4	6 / 0	2024-02-23
10.0.3	6 / 0	2023-09-07
10.0.2	6 / 0	2023-08-09
10.0.1	7 / 0	2023-08-02
10.0.0	7 / 0	2023-05-19
9.0.35	7 / 0	2023-04-27
9.0.34	7 / 0	2023-04-24
9.0.33	7 / 0	2023-04-23
9.0.32	7 / 0	2023-04-18
9.0.31	7 / 0	2023-04-13
9.0.30	7 / 0	2023-04-06
9.0.29	7 / 0	2023-04-04
9.0.28	7 / 0	2023-02-23
9.0.27	7 / 0	2023-02-14
9.0.26	7 / 0	2023-02-06
9.0.25	7 / 0	2023-02-01
9.0.24	7 / 0	2023-01-29
9.0.23	7 / 0	2023-01-26
9.0.22	7 / 0	2023-01-12
9.0.21	7 / 0	2022-12-21
9.0.20	7 / 0	2022-12-08
9.0.19	7 / 0	2022-12-07
9.0.18	7 / 0	2022-12-07
9.0.17	7 / 0	2022-11-14
9.0.16	7 / 0	2022-11-11
9.0.15	7 / 0	2022-11-07
9.0.14	7 / 0	2022-11-02
9.0.13	7 / 0	2022-11-02
9.0.12	7 / 0	2022-11-01
9.0.11	7 / 0	2022-11-01
9.0.10	7 / 0	2022-10-31
9.0.9	7 / 0	2022-10-27
9.0.8	6 / 0	2022-09-29
9.0.7	6 / 0	2022-09-29
9.0.6	6 / 0	2022-09-09
9.0.5	6 / 0	2022-09-05
9.0.4	6 / 0	2022-08-26
9.0.3	6 / 0	2022-08-12
9.0.2	6 / 0	2022-08-12
9.0.1	6 / 0	2022-08-10

Showing 100 of 571 Next page →

v12.0.16

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.0.15

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.0.14

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.0.13

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.0.12

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.0.11

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.0.10

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.0.9

1 finding

LOW No provenance attestation provenance

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

v12.0.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.

v12.0.3

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.

v12.0.2

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.

v11.1.3

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.

v11.1.2

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.

v11.1.1

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.

v11.1.0

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.

v11.0.0

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.

v10.2.23

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.

v10.2.22

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.

v10.2.20

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.

v10.2.19

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.

v10.2.18

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.

v10.2.14

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.

v10.2.12

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.

v10.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.

v10.2.9

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.

v10.2.8

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.

v10.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.

v10.2.5

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.

v10.2.3

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.

v10.2.2

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.

v10.2.1

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.

v10.1.3

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.

v10.1.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.1.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.1.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.29

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.28

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.27

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.26

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.25

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.24

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.23

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.22

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.21

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.20

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.19

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.18

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.17

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.0.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.

v10.0.15

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.

v10.0.14

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.

v10.0.13

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.

v10.0.12

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.

v10.0.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.

v10.0.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.

v10.0.9

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.

v10.0.8

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.

v10.0.7

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.

v10.0.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.

v10.0.5

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.