@omegagrid/code
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 package @omegagrid/code; Levenshtein match to 'cors' is coincidental, no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @omegagrid/code; Levenshtein match to 'zod' is coincidental, no impersonation intent. | ai | |
| phantom-deps | phantom-dep:ts-debounce | AI (phantom-deps): Declared in dependencies; referenced in config files is expected for this build setup. | ai | |
| phantom-deps | phantom-dep:vscode-loader | AI (phantom-deps): Monaco editor companion loader; config-only reference is expected. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): UI icon library; config-only reference is expected for this webcomponent package. | ai |
Versions (showing 16 of 219)
| Version | Deps | Published |
|---|---|---|
| 0.6.49 | 9 / 10 | |
| 0.6.48 | 9 / 10 | |
| 0.6.47 | 9 / 10 | |
| 0.6.46 | 9 / 10 | |
| 0.6.45 | 9 / 10 | |
| 0.6.44 | 9 / 10 | |
| 0.6.43 | 9 / 10 | |
| 0.6.42 | 9 / 10 | |
| 0.6.41 | 9 / 10 | |
| 0.6.40 | 9 / 10 | |
| 0.6.39 | 9 / 10 | |
| 0.6.38 | 9 / 10 | |
| 0.6.37 | 9 / 10 | |
| 0.6.36 | 9 / 10 | |
| 0.6.35 | 9 / 10 | |
| 0.6.34 | 9 / 10 |
v0.6.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.