@webgpu/types BSD-3-Clause 32 versions

@webgpu/types

npm Repository Homepage

This package defines Typescript types (`.d.ts`) for the upcoming [WebGPU standard](https://github.com/gpuweb/gpuweb/wiki/Implementation-Status).

32

Versions

BSD-3-Clause

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kaininokangztojishrekshao

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Both kangz and kainino are gpuweb org members; legitimate maintainer transition.	ai	2026/05/09

Versions (showing 32 of 32)

Version	Deps	Published
0.1.71	0 / 2	2026-06-24
0.1.70	0 / 2	2026-05-11
0.1.69	0 / 2	2026-01-13
0.1.68	0 / 2	2025-12-13
0.1.67	0 / 2	2025-12-02
0.1.66	0 / 2	2025-10-14
0.1.65	0 / 2	2025-09-15
0.1.64	0 / 2	2025-07-07
0.1.63	0 / 2	2025-06-27
0.1.62	0 / 2	2025-06-25
0.1.61	0 / 2	2025-05-28
0.1.60	0 / 2	2025-03-28
0.1.59	0 / 2	2025-03-24
0.1.58	0 / 2	2025-03-22
0.1.57	0 / 2	2025-03-18
0.1.56	0 / 2	2025-03-14
0.1.55	0 / 2	2025-03-04
0.1.54	0 / 2	2025-02-01
0.1.53	0 / 2	2025-01-15
0.1.52	0 / 2	2024-12-17
0.1.51	0 / 2	2024-11-05
0.1.50	0 / 2	2024-11-02
0.1.49	0 / 2	2024-10-15
0.1.48	0 / 2	2024-10-02
0.1.47	0 / 2	2024-09-30
0.1.46	0 / 2	2024-09-19
0.1.45	0 / 2	2024-09-12
0.1.44	0 / 2	2024-07-11
0.1.43	0 / 2	2024-06-21
0.1.42	0 / 2	2024-05-30
0.1.41	0 / 2	2024-05-29
0.1.38	0 / 2	2023-10-12

v0.1.71

1 finding

LOW No provenance attestation provenance

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

v0.1.66

2 findings

HIGH Publisher changed: kangz → kainino (on 2025-10-14) provenance

This version was published by a different npm account than previous versions on 2025-10-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.65

2 findings

HIGH Publisher changed: kangz → kainino (on 2025-09-15) provenance

This version was published by a different npm account than previous versions on 2025-09-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.64

2 findings

HIGH Publisher changed: kangz → kainino (on 2025-07-07) provenance

This version was published by a different npm account than previous versions on 2025-07-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.63

2 findings

HIGH Publisher changed: kangz → kainino (on 2025-06-27) provenance

This version was published by a different npm account than previous versions on 2025-06-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.62

2 findings

HIGH Publisher changed: kangz → kainino (on 2025-06-25) provenance

This version was published by a different npm account than previous versions on 2025-06-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.61

2 findings

HIGH Publisher changed: kangz → kainino (on 2025-05-28) provenance

This version was published by a different npm account than previous versions on 2025-05-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.60

1 finding

LOW No provenance attestation provenance

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

v0.1.59

1 finding

LOW No provenance attestation provenance

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

v0.1.58

1 finding

LOW No provenance attestation provenance

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

v0.1.57

1 finding

LOW No provenance attestation provenance

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

v0.1.56

1 finding

LOW No provenance attestation provenance

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

v0.1.55

1 finding

LOW No provenance attestation provenance

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

v0.1.54

1 finding

LOW No provenance attestation provenance

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

v0.1.53

1 finding

LOW No provenance attestation provenance

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

v0.1.52

1 finding

LOW No provenance attestation provenance

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

v0.1.51

1 finding

LOW No provenance attestation provenance

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

v0.1.50

1 finding

LOW No provenance attestation provenance

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

v0.1.49

1 finding

LOW No provenance attestation provenance

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

v0.1.48

1 finding

LOW No provenance attestation provenance

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

v0.1.47

1 finding

LOW No provenance attestation provenance

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

v0.1.46

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: toji → kainino (on 2024-09-19, known maintainer) provenance

This version was published by a different npm account (kainino) than the most recent previously approved version (toji) on 2024-09-19, but kainino is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.1.45

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: toji → kainino (on 2024-09-12, known maintainer) provenance

This version was published by a different npm account (kainino) than the most recent previously approved version (toji) on 2024-09-12, but kainino is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.1.44

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: kainino → toji (on 2024-07-11, known maintainer) provenance

This version was published by a different npm account (toji) than the most recent previously approved version (kainino) on 2024-07-11, but toji is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.1.43

1 finding

LOW No provenance attestation provenance

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

v0.1.42

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: kangz → kainino (on 2024-05-30, known maintainer) provenance

This version was published by a different npm account (kainino) than the most recent previously approved version (kangz) on 2024-05-30, but kainino is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.1.41

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: kangz → kainino (on 2024-05-29, known maintainer) provenance

This version was published by a different npm account (kainino) than the most recent previously approved version (kangz) on 2024-05-29, but kainino is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.