@xapp/stentor-service-salesforce
Service to interface the Salesforce CRM service
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Change is to CI/CD publisher (GitHub Actions), consistent with provenance improvement. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with CI takeover of publishing, not a hostile handoff. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Long-standing internal-org package, sparse metadata is normal for it. | ai |
Versions (showing 100 of 196)
| Version | Deps | Published |
|---|---|---|
| 1.86.0 | 1 / 11 | |
| 1.85.1 | 1 / 11 | |
| 1.80.3 | 1 / 11 | |
| 1.78.5 | 1 / 11 | |
| 1.78.2 | 1 / 11 | |
| 1.78.0 | 1 / 11 | |
| 1.77.2 | 1 / 11 | |
| 1.76.22 | 1 / 11 | |
| 1.76.20 | 1 / 11 | |
| 1.76.16 | 1 / 11 | |
| 1.76.12 | 1 / 11 | |
| 1.76.11 | 1 / 11 | |
| 1.76.10 | 1 / 11 | |
| 1.76.9 | 1 / 11 | |
| 1.76.6 | 1 / 11 | |
| 1.76.5 | 1 / 11 | |
| 1.76.4 | 1 / 11 | |
| 1.76.1 | 1 / 11 | |
| 1.74.24 | 1 / 11 | |
| 1.74.23 | 1 / 11 | |
| 1.74.22 | 1 / 11 | |
| 1.74.18 | 1 / 11 | |
| 1.74.14 | 1 / 11 | |
| 1.74.9 | 1 / 11 | |
| 1.73.19 | 1 / 11 | |
| 1.73.11 | 1 / 11 | |
| 1.73.6 | 1 / 11 | |
| 1.73.3 | 1 / 11 | |
| 1.73.1 | 1 / 11 | |
| 1.72.11 | 1 / 11 | |
| 1.72.8 | 1 / 11 | |
| 1.72.7 | 1 / 11 | |
| 1.72.4 | 1 / 11 | |
| 1.72.3 | 1 / 11 | |
| 1.71.29 | 1 / 11 | |
| 1.71.27 | 1 / 11 | |
| 1.71.24 | 1 / 11 | |
| 1.71.23 | 1 / 11 | |
| 1.71.21 | 1 / 11 | |
| 1.71.18 | 1 / 11 | |
| 1.71.12 | 1 / 11 | |
| 1.71.11 | 1 / 11 | |
| 1.71.9 | 1 / 11 | |
| 1.71.8 | 1 / 11 | |
| 1.71.4 | 1 / 11 | |
| 1.71.1 | 1 / 11 | |
| 1.70.50 | 1 / 11 | |
| 1.70.49 | 1 / 11 | |
| 1.70.47 | 1 / 11 | |
| 1.70.46 | 1 / 11 | |
| 1.70.44 | 1 / 11 | |
| 1.70.38 | 1 / 11 | |
| 1.70.35 | 1 / 11 | |
| 1.70.31 | 1 / 11 | |
| 1.70.19 | 1 / 11 | |
| 1.70.18 | 1 / 11 | |
| 1.70.16 | 1 / 11 | |
| 1.70.13 | 1 / 11 | |
| 1.70.11 | 1 / 11 | |
| 1.70.9 | 1 / 11 | |
| 1.70.8 | 1 / 11 | |
| 1.70.7 | 1 / 11 | |
| 1.70.6 | 1 / 11 | |
| 1.70.5 | 1 / 11 | |
| 1.70.3 | 1 / 11 | |
| 1.69.4 | 1 / 11 | |
| 1.69.2 | 1 / 11 | |
| 1.69.1 | 1 / 11 | |
| 1.69.0 | 1 / 11 | |
| 1.68.1 | 1 / 11 | |
| 1.66.10 | 1 / 11 | |
| 1.66.9 | 1 / 11 | |
| 1.66.8 | 1 / 11 | |
| 1.66.6 | 1 / 11 | |
| 1.66.4 | 1 / 11 | |
| 1.66.3 | 1 / 11 | |
| 1.66.0 | 1 / 11 | |
| 1.65.43 | 1 / 11 | |
| 1.65.41 | 1 / 11 | |
| 1.65.40 | 1 / 11 | |
| 1.65.39 | 1 / 11 | |
| 1.65.38 | 1 / 11 | |
| 1.65.35 | 1 / 11 | |
| 1.65.34 | 1 / 11 | |
| 1.65.33 | 1 / 11 | |
| 1.65.31 | 1 / 11 | |
| 1.65.30 | 1 / 11 | |
| 1.65.29 | 1 / 11 | |
| 1.65.28 | 1 / 11 | |
| 1.65.27 | 1 / 11 | |
| 1.65.26 | 1 / 11 | |
| 1.65.23 | 1 / 11 | |
| 1.65.21 | 1 / 11 | |
| 1.65.20 | 1 / 11 | |
| 1.65.17 | 1 / 11 | |
| 1.65.16 | 1 / 11 | |
| 1.65.14 | 1 / 11 | |
| 1.65.11 | 1 / 11 | |
| 1.65.10 | 1 / 11 | |
| 1.65.8 | 1 / 11 |
v1.86.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.