@salesforce/sdk-data
Runtime SDK for accessing Salesforce record data via GraphQL and REST from React web apps.
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Intentional for this internal Salesforce SDK package; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has 2432 approved packages without provenance; consistent pattern for this org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Salesforce SDK package; missing metadata is consistent across all versions, not a spam/malware indicator. | ai | |
| dependencies | unvetted-dep:@conduit-client/utils | AI (dependencies): Internal Salesforce/conduit-client ecosystem dep; stable pattern across versions from trusted publisher. | ai | |
| dependencies | unvetted-dep:@conduit-client/service-fetch-network | AI (dependencies): Internal Salesforce/conduit-client ecosystem dep; stable pattern across versions from trusted publisher. | ai | |
| phantom-deps | phantom-dep:@conduit-client/utils | AI (phantom-deps): Finding notes it's referenced in config files but not directly imported — stable false positive for this package. | ai |
Versions (showing 51 of 298)
| Version | Deps | Published |
|---|---|---|
| 1.135.0 | 3 / 3 | |
| 1.134.5 | 3 / 3 | |
| 1.134.4 | 3 / 3 | |
| 1.134.3 | 3 / 3 | |
| 1.134.2 | 3 / 3 | |
| 1.134.1 | 3 / 3 | |
| 1.134.0 | 3 / 3 | |
| 1.133.2 | 3 / 3 | |
| 1.133.1 | 3 / 3 | |
| 1.133.0 | 3 / 3 | |
| 1.132.0 | 3 / 3 | |
| 1.131.3 | 3 / 3 | |
| 1.131.2 | 3 / 3 | |
| 1.131.1 | 3 / 3 | |
| 1.131.0 | 3 / 3 | |
| 1.130.2 | 3 / 3 | |
| 1.130.1 | 3 / 3 | |
| 1.130.0 | 3 / 3 | |
| 1.129.1 | 3 / 3 | |
| 1.129.0 | 3 / 3 | |
| 1.128.0 | 3 / 3 | |
| 1.127.0 | 3 / 3 | |
| 1.126.0 | 3 / 3 | |
| 1.123.0 | 3 / 3 | |
| 1.122.2 | 3 / 3 | |
| 1.122.1 | 3 / 3 | |
| 1.122.0 | 3 / 3 | |
| 1.121.0 | 3 / 3 | |
| 1.120.7 | 3 / 3 | |
| 1.120.6 | 3 / 3 | |
| 1.120.4 | 3 / 3 | |
| 1.120.3 | 3 / 3 | |
| 1.120.2 | 3 / 3 | |
| 1.120.1 | 3 / 3 | |
| 1.120.0 | 3 / 3 | |
| 1.119.6 | 3 / 3 | |
| 1.119.5 | 3 / 3 | |
| 1.119.4 | 3 / 3 | |
| 1.119.3 | 3 / 3 | |
| 1.119.2 | 3 / 3 | |
| 1.119.1 | 3 / 3 | |
| 1.119.0 | 3 / 3 | |
| 1.118.4 | 3 / 3 | |
| 1.118.3 | 3 / 3 | |
| 1.118.2 | 3 / 3 | |
| 1.118.1 | 3 / 3 | |
| 1.118.0 | 3 / 3 | |
| 1.117.5 | 3 / 3 | |
| 1.117.4 | 3 / 3 | |
| 1.117.3 | 3 / 3 | |
| 1.117.2 | 3 / 3 |
v1.135.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.134.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.134.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.134.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.134.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.134.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.134.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.133.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.133.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.133.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.131.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.131.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.131.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.131.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.130.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.130.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.130.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.129.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.129.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lwc-admin) than the most recent previously approved version (ravi.jayaramappa) on 2026-04-23, but lwc-admin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.128.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lwc-admin) than the most recent previously approved version (ravi.jayaramappa) on 2026-04-23, but lwc-admin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.127.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lwc-admin) than the most recent previously approved version (ravi.jayaramappa) on 2026-04-22, but lwc-admin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.126.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lwc-admin) than the most recent previously approved version (ravi.jayaramappa) on 2026-04-22, but lwc-admin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.123.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.122.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.122.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.122.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.121.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ravi.jayaramappa) than the most recent previously approved version (lwc-admin) on 2026-04-07, but ravi.jayaramappa is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.120.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.119.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.119.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.119.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.119.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.119.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.119.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.119.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.118.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.118.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.118.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.118.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.118.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.117.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.117.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.117.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.117.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.