@omegagrid/grid
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped datagrid package; Levenshtein match to 'uuid' is a false positive with no semantic similarity. | ai | |
| phantom-deps | phantom-dep:sha1 | AI (phantom-deps): sha1 is a declared runtime dep with @types/sha1 in devDeps; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:@stdlib/stats | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic misfires — may be used indirectly via grid-core or similar. | ai |
Versions (showing 13 of 216)
| Version | Deps | Published |
|---|---|---|
| 0.6.46 | 12 / 11 | |
| 0.6.45 | 12 / 11 | |
| 0.6.44 | 12 / 11 | |
| 0.6.43 | 12 / 11 | |
| 0.6.42 | 12 / 11 | |
| 0.6.41 | 12 / 11 | |
| 0.6.40 | 12 / 11 | |
| 0.6.39 | 12 / 11 | |
| 0.6.38 | 12 / 11 | |
| 0.6.37 | 12 / 11 | |
| 0.6.36 | 12 / 11 | |
| 0.6.35 | 12 / 11 | |
| 0.6.34 | 12 / 11 |
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.