← Home

@salesforce/plugin-sobject

npm Repository Homepage
100
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

ire-npm-team-userjimjagsalesforce-releasesjasonschroeder-sfdcmobifylwc-adminsalesforce-admin

Keywords

forcesalesforcesalesforcedxsfsf-pluginsfdxsfdx-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): salesforce-admin is a Salesforce org account; adding it reflects consolidation of publishing under a centralized account, consistent with Salesforce's org-wide publishing practices. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of individual developer accounts in favor of a centralized org account (salesforce-admin) is consistent with Salesforce's publishing consolidation; not indicative of takeover. ai
phantom-deps phantom-dep:@salesforce/kit AI (phantom-deps): @salesforce/kit is a declared runtime dep in the same org scope; phantom-dep false positive for this package. ai

Versions (showing 100 of 164)

Version Deps Published
1.4.124 10 / 9
1.4.123 10 / 9
1.4.122 10 / 9
1.4.121 10 / 9
1.4.120 10 / 9
1.4.119 10 / 9
1.4.117 10 / 9
1.4.116 10 / 9
1.4.115 10 / 9
1.4.114 10 / 9
1.4.113 10 / 9
1.4.112 10 / 9
1.4.111 10 / 9
1.4.110 10 / 9
1.4.109 10 / 9
1.4.108 10 / 9
1.4.107 10 / 9
1.4.106 10 / 9
1.4.105 10 / 9
1.4.104 10 / 9
1.4.103 10 / 9
1.4.102 10 / 9
1.4.101 10 / 9
1.4.100 10 / 9
1.4.99 10 / 9
1.4.98 10 / 9
1.4.97 10 / 9
1.4.96 10 / 9
1.4.95 10 / 9
1.4.94 10 / 9
1.4.93 10 / 9
1.4.92 10 / 9
1.4.91 10 / 9
1.4.90 10 / 9
1.4.89 10 / 9
1.4.88 10 / 9
1.4.87 10 / 9
1.4.86 10 / 9
1.4.85 10 / 9
1.4.84 10 / 9
1.4.83 10 / 9
1.4.82 10 / 9
1.4.81 10 / 9
1.4.80 10 / 9
1.4.79 10 / 9
1.4.78 10 / 9
1.4.77 10 / 9
1.4.76 10 / 9
1.4.73 10 / 9
1.4.72 10 / 9
1.4.71 10 / 9
1.4.70 10 / 9
1.4.69 10 / 9
1.4.68 10 / 9
1.4.67 10 / 9
1.4.66 10 / 9
1.4.65 10 / 9
1.4.64 10 / 9
1.4.63 10 / 9
1.4.62 10 / 9
1.4.61 10 / 9
1.4.60 10 / 9
1.4.59 10 / 9
1.4.58 10 / 9
1.4.57 10 / 9
1.4.56 10 / 9
1.4.55 10 / 9
1.4.54 10 / 9
1.4.53 10 / 9
1.4.52 10 / 9
1.4.51 10 / 9
1.4.50 10 / 9
1.4.49 10 / 9
1.4.48 10 / 9
1.4.47 10 / 9
1.4.46 10 / 9
1.4.45 10 / 9
1.4.44 10 / 9
1.4.43 10 / 9
1.4.42 10 / 9
1.4.41 10 / 9
1.4.40 10 / 9
1.4.39 10 / 9
1.4.38 10 / 9
1.4.37 10 / 9
1.4.36 10 / 9
1.4.35 10 / 9
1.4.34 10 / 9
1.4.33 10 / 9
1.4.32 10 / 9
1.4.31 10 / 9
1.4.30 10 / 9
1.4.29 10 / 9
1.4.28 10 / 9
1.4.27 10 / 9
1.4.26 10 / 9
1.4.25 10 / 9
1.4.24 10 / 9
1.4.23 10 / 9
1.4.22 10 / 9
Showing 100 of 164 Next page →

v1.4.124

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.123

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.122

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.121

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.120

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.119

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.55

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.54

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.53

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.52

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.51

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.50

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.49

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.48

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.46

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.44

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.43

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.42

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.41

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.40

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.39

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.38

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.37

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.36

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.34

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.33

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.