@omegagrid/editor
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lit | AI (phantom-deps): Re-exported via @omegagrid/* dependencies; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:lit-html | AI (phantom-deps): Re-exported via @omegagrid/* dependencies; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:ts-debounce | AI (phantom-deps): Re-exported via @omegagrid/* dependencies; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@omegagrid/core | AI (phantom-deps): Same-org scoped re-export; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@omegagrid/form | AI (phantom-deps): Same-org scoped re-export; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@omegagrid/grid | AI (phantom-deps): Same-org scoped re-export; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@omegagrid/tabs | AI (phantom-deps): Same-org scoped re-export; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@omegagrid/tree | AI (phantom-deps): Same-org scoped re-export; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@omegagrid/toolbar | AI (phantom-deps): Same-org scoped re-export; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@omegagrid/commands | AI (phantom-deps): Same-org scoped re-export; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@omegagrid/localize | AI (phantom-deps): Same-org scoped re-export; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@omegagrid/statusbar | AI (phantom-deps): Same-org scoped re-export; stable monorepo pattern. | ai |
Versions (showing 14 of 217)
| Version | Deps | Published |
|---|---|---|
| 0.6.47 | 12 / 20 | |
| 0.6.46 | 12 / 20 | |
| 0.6.45 | 12 / 20 | |
| 0.6.44 | 12 / 20 | |
| 0.6.43 | 12 / 20 | |
| 0.6.42 | 12 / 20 | |
| 0.6.41 | 12 / 20 | |
| 0.6.40 | 12 / 20 | |
| 0.6.39 | 12 / 20 | |
| 0.6.38 | 12 / 20 | |
| 0.6.37 | 12 / 20 | |
| 0.6.36 | 12 / 20 | |
| 0.6.35 | 12 / 20 | |
| 0.6.34 | 12 / 20 |
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.