@salesforce/lds-luvio-onestore-graphql-parser
Re-export of the @conduit-client/graphql package for use in adapters
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@luvio/onestore-graphql-parser | AI (dependencies): First-party Luvio dependency matching the package's documented re-export purpose; stable across versions. | ai | |
| provenance | publisher-changed | AI (provenance): lwc-admin is a well-established Salesforce admin account; publisher rotation to this account is consistent with org-level CI/CD consolidation. | ai |
Versions (showing 78 of 78)
| Version | Deps | Published |
|---|---|---|
| 1.450.0 | 1 / 0 | |
| 1.449.0 | 1 / 0 | |
| 1.448.0 | 1 / 0 | |
| 1.447.1 | 1 / 0 | |
| 1.447.0 | 1 / 0 | |
| 1.446.0 | 1 / 0 | |
| 1.445.0 | 1 / 0 | |
| 1.444.0 | 1 / 0 | |
| 1.443.0 | 1 / 0 | |
| 1.442.0 | 1 / 0 | |
| 1.441.0 | 1 / 0 | |
| 1.440.0 | 1 / 0 | |
| 1.439.0 | 1 / 0 | |
| 1.438.1 | 1 / 0 | |
| 1.438.0 | 1 / 0 | |
| 1.437.0 | 1 / 0 | |
| 1.436.0 | 1 / 0 | |
| 1.435.1 | 1 / 0 | |
| 1.435.0 | 1 / 0 | |
| 1.434.0 | 1 / 0 | |
| 1.433.0 | 1 / 0 | |
| 1.432.0 | 1 / 0 | |
| 1.431.0 | 1 / 0 | |
| 1.430.0 | 1 / 0 | |
| 1.429.0 | 1 / 0 | |
| 1.428.0 | 1 / 0 | |
| 1.427.0 | 1 / 0 | |
| 1.426.1 | 1 / 0 | |
| 1.425.0 | 1 / 0 | |
| 1.424.0 | 1 / 0 | |
| 1.423.0 | 1 / 0 | |
| 1.422.0 | 1 / 0 | |
| 1.421.1 | 1 / 0 | |
| 1.421.0 | 1 / 0 | |
| 1.420.0 | 1 / 0 | |
| 1.419.0 | 1 / 0 | |
| 1.418.0 | 1 / 0 | |
| 1.417.0 | 1 / 0 | |
| 1.416.1 | 1 / 0 | |
| 1.416.0 | 1 / 0 | |
| 1.415.0 | 1 / 0 | |
| 1.414.1 | 1 / 0 | |
| 1.414.0 | 1 / 0 | |
| 1.413.0 | 1 / 0 | |
| 1.412.1 | 1 / 0 | |
| 1.412.0 | 1 / 0 | |
| 1.411.0 | 1 / 0 | |
| 1.410.1 | 1 / 0 | |
| 1.410.0 | 1 / 0 | |
| 1.409.0 | 1 / 0 | |
| 1.405.0 | 1 / 0 | |
| 1.404.0 | 1 / 0 | |
| 1.403.0 | 1 / 0 | |
| 1.402.0 | 1 / 0 | |
| 1.401.0 | 1 / 0 | |
| 1.400.0 | 1 / 0 | |
| 1.399.0 | 1 / 0 | |
| 1.398.0 | 1 / 0 | |
| 1.397.0 | 1 / 0 | |
| 1.396.0 | 1 / 0 | |
| 1.395.0 | 1 / 0 | |
| 1.394.0 | 1 / 0 | |
| 1.393.0 | 1 / 0 | |
| 1.392.0 | 1 / 0 | |
| 1.391.0 | 1 / 0 | |
| 1.390.0 | 1 / 0 | |
| 1.389.2 | 1 / 0 | |
| 1.389.1 | 1 / 0 | |
| 1.389.0 | 1 / 0 | |
| 1.388.0 | 1 / 0 | |
| 1.387.0 | 1 / 0 | |
| 1.386.0 | 1 / 0 | |
| 1.385.0 | 1 / 0 | |
| 1.384.0 | 1 / 0 | |
| 1.383.0 | 1 / 0 | |
| 1.382.0 | 1 / 0 | |
| 1.381.0 | 1 / 0 | |
| 1.380.0 | 1 / 0 |
v1.450.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.449.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.448.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.447.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.447.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.398.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.397.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.394.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.390.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.389.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.389.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.388.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.386.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.385.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.