@galacean/engine-xr MIT 78 versions

@galacean/engine-xr

npm Repository Homepage

`@galacean/engine-xr` is the implementation layer of XRManager and is a necessary package for developing XR applications.

78

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

yiqiimchenjianchengkong.zxxeyworldwideyinjieruimeng.sugl3336563zhanyingweizhuxudongjohanzhumrkou47husongluzhuangjujiefeyabibi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
email-domain	unclaimed-email:yufangjun.com	AI (email-domain): SLSA provenance attestation via Sigstore mitigates the domain hijacking risk for this established monorepo package.	ai	2026/04/30

Versions (showing 78 of 78)

Version	Deps	Published
1.6.13	0 / 2	2025-12-29
1.6.12	0 / 2	2025-12-26
1.6.11	0 / 2	2025-11-28
1.6.10	0 / 2	2025-11-28
1.6.9	0 / 2	2025-11-28
1.6.8	0 / 2	2025-11-28
1.6.7	0 / 2	2025-10-24
1.6.6	0 / 2	2025-10-10
1.6.5	0 / 2	2025-09-23
1.6.4	0 / 2	2025-09-23
1.6.3	0 / 2	2025-09-23
1.6.2	0 / 2	2025-09-22
1.6.1	0 / 2	2025-09-21
1.6.0	0 / 2	2025-09-18
1.5.16	0 / 2	2025-12-04
1.5.15	0 / 2	2025-09-21
1.5.14	0 / 2	2025-09-04
1.5.13	0 / 2	2025-08-22
1.5.12	0 / 2	2025-07-15
1.5.11	0 / 2	2025-07-11
1.5.10	0 / 2	2025-07-02
1.5.9	0 / 2	2025-06-24
1.5.8	0 / 2	2025-06-18
1.5.7	0 / 2	2025-05-29
1.5.6	0 / 2	2025-05-28
1.5.5	0 / 2	2025-05-28
1.5.4	0 / 2	2025-05-28
1.5.3	0 / 2	2025-05-27
1.5.2	0 / 2	2025-05-26
1.5.1	0 / 2	2025-05-26
1.5.0	0 / 2	2025-05-22
1.4.16	0 / 2	2025-05-14
1.4.15	0 / 2	2025-04-23
1.4.14	0 / 2	2025-04-18
1.4.13	0 / 2	2025-04-17
1.4.12	0 / 2	2025-03-04
1.4.11	0 / 2	2025-03-04
1.4.10	0 / 2	2025-03-03
1.4.9	0 / 2	2025-02-18
1.4.8	0 / 2	2025-02-12
1.4.7	0 / 2	2025-02-08
1.4.6	0 / 2	2025-02-07
1.4.5	0 / 2	2025-01-24
1.4.4	0 / 2	2025-01-23
1.4.3	0 / 2	2025-01-21
1.4.2	0 / 2	2025-01-20
1.4.1	0 / 2	2025-01-17
1.4.0	0 / 2	2025-01-16
1.3.30	0 / 2	2025-04-24
1.3.29	0 / 2	2025-04-24
1.3.28	0 / 2	2025-04-23
1.3.27	0 / 2	2025-04-22
1.3.26	0 / 2	2025-02-14
1.3.25	0 / 2	2024-12-17
1.3.24	0 / 2	2024-11-15
1.3.23	0 / 2	2024-11-13
1.3.22	0 / 2	2024-11-13
1.3.21	0 / 2	2024-11-13
1.3.20	0 / 2	2024-11-11
1.3.19	0 / 2	2024-11-07
1.3.18	0 / 2	2024-11-07
1.3.17	0 / 2	2024-11-06
1.3.16	0 / 2	2024-11-05
1.3.15	0 / 2	2024-10-30
1.3.14	0 / 2	2024-10-30
1.3.12	0 / 2	2024-09-24
1.3.11	0 / 2	2024-09-11
1.3.10	0 / 2	2024-08-30
1.3.9	0 / 2	2024-08-28
1.3.8	0 / 2	2024-08-22
1.3.7	0 / 2	2024-08-20
1.3.6	0 / 2	2024-08-13
1.3.5	0 / 2	2024-08-08
1.3.3	0 / 2	2024-08-07
1.3.2	0 / 2	2024-08-06
1.3.1	0 / 2	2024-08-05
1.3.0	0 / 2	2024-08-02
1.2.0	0 / 2	2024-07-24

v1.4.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.

v1.4.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.

v1.4.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.

v1.4.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.

v1.4.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.

v1.4.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.

v1.4.9

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.

v1.4.8

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.

v1.4.7

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.

v1.4.6

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.

v1.4.5

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.

v1.4.4

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.

v1.4.3

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.

v1.4.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.

v1.4.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.

v1.4.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.

v1.3.30

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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.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.

v1.3.9

2 findings

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.

INFO Publisher changed: gl3336563 → husong (on 2024-08-28, now via trusted publisher with provenance) provenance

This version was published by a different npm account (husong) than the most recent previously approved version (gl3336563) on 2024-08-28, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v1.3.8

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: gl3336563 → zhanyingwei (on 2024-08-22, known maintainer) provenance

This version was published by a different npm account (zhanyingwei) than the most recent previously approved version (gl3336563) on 2024-08-22, but zhanyingwei 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.

v1.3.7

1 finding

LOW No provenance attestation provenance

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

v1.3.6

1 finding

LOW No provenance attestation provenance

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

v1.3.5

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: husong → gl3336563 (on 2024-08-08, known maintainer) provenance

This version was published by a different npm account (gl3336563) than the most recent previously approved version (husong) on 2024-08-08, but gl3336563 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.

v1.3.3

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: husong → gl3336563 (on 2024-08-07, known maintainer) provenance

This version was published by a different npm account (gl3336563) than the most recent previously approved version (husong) on 2024-08-07, but gl3336563 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.

v1.3.2

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: gl3336563 → husong (on 2024-08-06, known maintainer) provenance

This version was published by a different npm account (husong) than the most recent previously approved version (gl3336563) on 2024-08-06, but husong 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.

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.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.