@gcforms/core
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): Scoped @gcforms/core package from Canadian Digital Service; not a typosquat of cors, just a short name within a legitimate org scope. | ai | |
| phantom-deps | phantom-dep:tsdown | AI (phantom-deps): tsdown is used as a build tool configured via package.json tsdown field; phantom-dep heuristic fires but it's a legitimate build dependency. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.2.4 | 3 / 1 | |
| 2.2.3 | 2 / 1 | |
| 2.2.2 | 2 / 1 | |
| 2.2.1 | 2 / 1 | |
| 2.2.0 | 2 / 1 | |
| 2.1.0 | 2 / 1 | |
| 2.0.3 | 2 / 1 | |
| 2.0.2 | 2 / 1 | |
| 2.0.1 | 2 / 1 |
v2.2.4
2 findingsPackage name '@gcforms/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.
v2.2.3
2 findingsPackage name '@gcforms/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.
v2.2.2
2 findingsPackage name '@gcforms/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.
v2.2.1
2 findingsPackage name '@gcforms/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.
v2.2.0
2 findingsPackage name '@gcforms/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.
v2.1.0
2 findingsPackage name '@gcforms/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.
v2.0.3
2 findingsPackage name '@gcforms/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.
v2.0.2
2 findingsPackage name '@gcforms/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.
v2.0.1
2 findingsPackage name '@gcforms/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.