@gem-sdk/core
```bash GP_BASE_ASSET_URL=https://assets.gemcommerce.xyz ```
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @gem-sdk/core is a scoped SDK package; name similarity to 'cors' is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:cssjson | AI (phantom-deps): cssjson is a declared dependency used in config/build context; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 16.3.4 | 8 / 3 | |
| 16.0.0 | 8 / 3 | |
| 15.0.7 | 8 / 3 | |
| 15.0.5 | 8 / 3 | |
| 14.0.0 | 8 / 3 | |
| 13.1.6 | 7 / 3 | |
| 13.1.3 | 7 / 3 | |
| 13.1.0 | 7 / 3 | |
| 13.0.0 | 7 / 3 | |
| 11.2.0 | 7 / 3 | |
| 8.0.1 | 7 / 3 | |
| 8.0.0 | 7 / 3 | |
| 7.0.0 | 7 / 3 |
v16.0.0
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.7
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.5
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.0
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.6
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.3
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.0
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.0
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
2 findingsPackage name '@gem-sdk/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.