@soonspacejs/plugin-first-person-controls
FirstPersonControls plugin for SoonSpace.js
Supply chain provenance
Status for the latest visible version.
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
Keywords
Versions (showing 100 of 371)
| Version | Deps | Published |
|---|---|---|
| 2.15.16 | 0 / 0 | |
| 2.15.15 | 0 / 0 | |
| 2.15.14 | 0 / 0 | |
| 2.15.13 | 0 / 0 | |
| 2.15.12 | 0 / 0 | |
| 2.15.11 | 0 / 0 | |
| 2.15.10 | 0 / 0 | |
| 2.15.9 | 0 / 0 | |
| 2.15.8 | 0 / 0 | |
| 2.15.4 | 0 / 0 | |
| 2.15.3 | 0 / 0 | |
| 2.15.1 | 0 / 0 | |
| 2.15.0 | 0 / 0 | |
| 2.14.37 | 0 / 0 | |
| 2.14.35 | 0 / 0 | |
| 2.14.34 | 0 / 0 | |
| 2.14.33 | 0 / 0 | |
| 2.14.32 | 0 / 0 | |
| 2.14.31 | 0 / 0 | |
| 2.14.30 | 0 / 0 | |
| 2.14.29 | 0 / 0 | |
| 2.14.28 | 0 / 0 | |
| 2.14.27 | 0 / 0 | |
| 2.14.26 | 0 / 0 | |
| 2.14.24 | 0 / 0 | |
| 2.14.23 | 0 / 0 | |
| 2.14.21 | 0 / 0 | |
| 2.14.20 | 0 / 0 | |
| 2.14.18 | 0 / 0 | |
| 2.14.17 | 0 / 0 | |
| 2.14.13 | 0 / 0 | |
| 2.14.12 | 0 / 0 | |
| 2.14.11 | 0 / 0 | |
| 2.14.10 | 0 / 0 | |
| 2.14.9 | 0 / 0 | |
| 2.14.8 | 0 / 0 | |
| 2.14.7 | 0 / 0 | |
| 2.14.6 | 0 / 0 | |
| 2.14.5 | 0 / 0 | |
| 2.14.2 | 0 / 0 | |
| 2.14.1 | 0 / 0 | |
| 2.14.0 | 0 / 0 | |
| 2.13.17 | 0 / 0 | |
| 2.13.12 | 0 / 0 | |
| 2.13.11 | 0 / 0 | |
| 2.13.10 | 0 / 0 | |
| 2.13.9 | 0 / 0 | |
| 2.13.8 | 0 / 0 | |
| 2.13.7 | 0 / 0 | |
| 2.13.6 | 0 / 0 | |
| 2.13.5 | 0 / 0 | |
| 2.13.4 | 0 / 0 | |
| 2.13.2 | 0 / 0 | |
| 2.13.1 | 0 / 0 | |
| 2.13.0 | 0 / 0 | |
| 2.12.2 | 0 / 0 | |
| 2.12.1 | 0 / 0 | |
| 2.12.0 | 0 / 0 | |
| 2.11.71 | 0 / 0 | |
| 2.11.70 | 0 / 0 | |
| 2.11.69 | 0 / 0 | |
| 2.11.68 | 0 / 0 | |
| 2.11.67 | 0 / 0 | |
| 2.11.66 | 0 / 0 | |
| 2.11.65 | 0 / 0 | |
| 2.11.64 | 0 / 0 | |
| 2.11.63 | 0 / 0 | |
| 2.11.62 | 0 / 0 | |
| 2.11.61 | 0 / 0 | |
| 2.11.60 | 0 / 0 | |
| 2.11.59 | 0 / 0 | |
| 2.11.58 | 0 / 0 | |
| 2.11.57 | 0 / 0 | |
| 2.11.56 | 0 / 0 | |
| 2.11.55 | 0 / 0 | |
| 2.11.54 | 0 / 0 | |
| 2.11.53 | 0 / 0 | |
| 2.11.52 | 0 / 0 | |
| 2.11.51 | 0 / 0 | |
| 2.11.50 | 0 / 0 | |
| 2.11.49 | 0 / 0 | |
| 2.11.48 | 0 / 0 | |
| 2.11.47 | 0 / 0 | |
| 2.11.46 | 0 / 0 | |
| 2.11.45 | 0 / 0 | |
| 2.11.44 | 0 / 0 | |
| 2.11.43 | 0 / 0 | |
| 2.11.42 | 0 / 0 | |
| 2.11.41 | 0 / 0 | |
| 2.11.40 | 0 / 0 | |
| 2.11.39 | 0 / 0 | |
| 2.11.38 | 0 / 0 | |
| 2.11.37 | 0 / 0 | |
| 2.11.36 | 0 / 0 | |
| 2.11.35 | 0 / 0 | |
| 2.11.34 | 0 / 0 | |
| 2.11.33 | 0 / 0 | |
| 2.11.32 | 0 / 0 | |
| 2.11.31 | 0 / 0 | |
| 2.11.30 | 0 / 0 |
v2.15.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chjxx) than the most recent previously approved version (jiangqi) on 2026-07-24, but chjxx 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.
v2.15.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jiangqi) than the most recent previously approved version (chjxx) on 2026-07-08, but jiangqi 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.
v2.13.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jiangqi) than the most recent previously approved version (guobinyong) on 2025-04-14, but jiangqi 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.
v2.13.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (guobinyong) than the most recent previously approved version (jiangqi) on 2025-04-10, but guobinyong 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.
v2.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.