@salesforce/lds-graphql-parser
LDS graphql parser for SFDC
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-graphql-parser | AI (dependencies): npm alias for @luvio/graphql-parser, a Salesforce internal package consistent with this package's purpose. | ai | |
| dependencies | unvetted-dep:onestore-graphql-parser | AI (dependencies): npm alias for @luvio/graphql-parser, a Salesforce internal package consistent with this package's purpose. | ai | |
| phantom-deps | phantom-dep:luvio-graphql-parser | AI (phantom-deps): npm alias for @luvio/graphql-parser; referenced in rollup config, not directly imported in source — stable false positive. | ai | |
| phantom-deps | phantom-dep:onestore-graphql-parser | AI (phantom-deps): npm alias for @luvio/graphql-parser; referenced in rollup config, not directly imported in source — stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Salesforce LDS monorepo package; no provenance is consistent across all versions in this family. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.txt | AI (license): Standard Salesforce proprietary license format used consistently across this package family. | ai |
Versions (showing 54 of 154)
| Version | Deps | Published |
|---|---|---|
| 1.340.0 | 1 / 0 | |
| 1.339.0 | 1 / 0 | |
| 1.338.0 | 1 / 0 | |
| 1.337.0 | 1 / 0 | |
| 1.336.0 | 1 / 0 | |
| 1.335.0 | 1 / 0 | |
| 1.334.0 | 1 / 0 | |
| 1.333.0 | 1 / 0 | |
| 1.332.0 | 1 / 0 | |
| 1.331.0 | 1 / 0 | |
| 1.330.0 | 1 / 0 | |
| 1.329.1 | 1 / 0 | |
| 1.329.0 | 1 / 0 | |
| 1.328.0 | 1 / 0 | |
| 1.327.0 | 1 / 0 | |
| 1.326.0 | 1 / 0 | |
| 1.325.0 | 1 / 0 | |
| 1.324.0 | 1 / 0 | |
| 1.323.0 | 1 / 0 | |
| 1.322.0 | 1 / 0 | |
| 1.321.0 | 1 / 0 | |
| 1.320.0 | 1 / 0 | |
| 1.319.0 | 1 / 0 | |
| 1.318.0 | 1 / 0 | |
| 1.317.0 | 1 / 0 | |
| 1.316.0 | 1 / 0 | |
| 1.315.0 | 1 / 0 | |
| 1.314.0 | 1 / 0 | |
| 1.313.0 | 1 / 0 | |
| 1.312.1 | 1 / 0 | |
| 1.312.0 | 1 / 0 | |
| 1.311.1 | 1 / 0 | |
| 1.311.0 | 1 / 0 | |
| 1.310.0 | 1 / 0 | |
| 1.309.0 | 1 / 0 | |
| 1.308.0 | 1 / 0 | |
| 1.307.0 | 1 / 0 | |
| 1.306.0 | 1 / 0 | |
| 1.305.0 | 1 / 0 | |
| 1.304.0 | 1 / 0 | |
| 1.303.0 | 1 / 0 | |
| 1.302.0 | 1 / 0 | |
| 1.301.0 | 1 / 0 | |
| 1.300.0 | 1 / 0 | |
| 1.299.0 | 1 / 0 | |
| 1.298.0 | 1 / 0 | |
| 1.297.0 | 1 / 0 | |
| 1.296.1 | 1 / 0 | |
| 1.296.0 | 1 / 0 | |
| 1.295.0 | 1 / 0 | |
| 1.294.0 | 1 / 0 | |
| 1.293.0 | 1 / 0 | |
| 1.292.0 | 1 / 0 | |
| 1.291.0 | 1 / 0 |
v1.340.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.339.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.338.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.337.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.336.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.335.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.334.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.333.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.332.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.331.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.330.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.329.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.329.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.328.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.327.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.326.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.325.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.324.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.323.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.322.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.321.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.320.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.319.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.318.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.317.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.316.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.315.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.314.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.313.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.312.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.312.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.311.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.311.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.310.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.309.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.308.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.307.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.306.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.305.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.304.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.303.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.302.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.301.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.300.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.299.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.298.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.297.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.296.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.296.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.295.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.294.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.293.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.292.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.291.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.