@gct-paas/word
GCT 在线 word
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:resize-observer-polyfill | AI (phantom-deps): Browser polyfill; config-referenced, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@gct-paas/api | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic not meaningful here. | ai | |
| phantom-deps | phantom-dep:async-validator | AI (phantom-deps): Form validation lib; config-referenced, stable false positive for this Vue library. | ai | |
| phantom-deps | phantom-dep:less | AI (phantom-deps): CSS preprocessor referenced in build config, not direct import; normal for Vue component libraries. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Utility lib used via build config/tree-shaking; phantom-dep heuristic false positive for this package type. | ai | |
| phantom-deps | phantom-dep:vue-color | AI (phantom-deps): UI component dep; referenced in config, stable false positive for this Vue library. | ai | |
| phantom-deps | phantom-dep:hotkeys-js | AI (phantom-deps): Keyboard shortcut lib; config-referenced, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): Math utility; config-referenced, stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @gct-paas/word is a Vue Word editor; edit-distance match to 'zod' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @gct-paas/word is a Vue Word editor; edit-distance match to 'cors' is coincidental. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.1.46 | 12 / 15 | |
| 0.1.45 | 12 / 15 | |
| 0.1.44 | 12 / 15 | |
| 0.1.43 | 12 / 15 | |
| 0.1.42 | 12 / 15 | |
| 0.1.41 | 12 / 15 | |
| 0.1.39 | 11 / 15 | |
| 0.1.38 | 11 / 15 | |
| 0.1.37 | 10 / 15 | |
| 0.1.36 | 10 / 15 | |
| 0.1.35 | 10 / 15 | |
| 0.1.34 | 10 / 15 | |
| 0.1.33 | 10 / 15 | |
| 0.1.32 | 10 / 15 | |
| 0.1.31 | 10 / 15 | |
| 0.1.30 | 10 / 15 | |
| 0.1.29 | 10 / 15 | |
| 0.1.27 | 10 / 15 | |
| 0.1.26 | 10 / 15 | |
| 0.1.25 | 10 / 15 | |
| 0.1.24 | 10 / 15 | |
| 0.1.23 | 10 / 15 | |
| 0.1.22 | 10 / 15 | |
| 0.1.21 | 10 / 15 | |
| 0.1.20 | 10 / 15 | |
| 0.1.19 | 10 / 15 | |
| 0.1.18 | 10 / 15 | |
| 0.1.17 | 11 / 15 | |
| 0.1.16 | 11 / 15 | |
| 0.1.15 | 11 / 15 | |
| 0.1.14 | 11 / 14 | |
| 0.1.13 | 11 / 14 | |
| 0.1.12 | 11 / 14 | |
| 0.1.11 | 11 / 14 | |
| 0.1.10 | 11 / 14 | |
| 0.1.9 | 11 / 14 | |
| 0.1.8 | 11 / 14 | |
| 0.1.7 | 11 / 14 | |
| 0.1.6 | 11 / 14 | |
| 0.1.5 | 11 / 14 |
v0.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.