@goldenhippo/hippo-salesforce-service
This package allows you to interact with the Salesforce Base Package via REST. It requires Salesforce credentials, a Redis instance and access to your Heroku Connect database.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv is listed as a runtime dependency in package.json; phantom-dep false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Internal/private-org package; lack of Sigstore provenance is consistent across all 97 versions. | ai |
Versions (showing 100 of 101)
| Version | Deps | Published |
|---|---|---|
| 1.23.0 | 7 / 23 | |
| 1.22.2 | 7 / 23 | |
| 1.22.1 | 7 / 23 | |
| 1.22.0 | 7 / 23 | |
| 1.21.5 | 7 / 23 | |
| 1.21.4 | 7 / 23 | |
| 1.21.3 | 7 / 23 | |
| 1.21.2 | 7 / 23 | |
| 1.21.1 | 7 / 23 | |
| 1.21.0 | 7 / 23 | |
| 1.20.1 | 7 / 23 | |
| 1.20.0 | 7 / 23 | |
| 1.19.3 | 7 / 23 | |
| 1.19.2 | 7 / 23 | |
| 1.19.1 | 7 / 23 | |
| 1.19.0 | 7 / 23 | |
| 1.18.1 | 7 / 23 | |
| 1.18.0 | 7 / 23 | |
| 1.17.2 | 7 / 23 | |
| 1.17.1 | 7 / 23 | |
| 1.17.0 | 7 / 23 | |
| 1.16.2 | 7 / 23 | |
| 1.16.1 | 7 / 23 | |
| 1.16.0 | 7 / 23 | |
| 1.15.0 | 7 / 23 | |
| 1.14.6 | 7 / 23 | |
| 1.14.5 | 7 / 23 | |
| 1.14.4 | 7 / 23 | |
| 1.14.3 | 7 / 23 | |
| 1.14.2 | 7 / 23 | |
| 1.14.1 | 7 / 23 | |
| 1.14.0 | 7 / 23 | |
| 1.13.10 | 7 / 23 | |
| 1.13.9 | 7 / 23 | |
| 1.13.8 | 7 / 23 | |
| 1.13.7 | 7 / 23 | |
| 1.13.6 | 7 / 23 | |
| 1.13.5 | 7 / 22 | |
| 1.13.4 | 7 / 22 | |
| 1.13.3 | 7 / 22 | |
| 1.13.2 | 7 / 22 | |
| 1.13.1 | 7 / 22 | |
| 1.13.0 | 7 / 22 | |
| 1.12.1 | 7 / 22 | |
| 1.12.0 | 7 / 22 | |
| 1.11.1 | 7 / 22 | |
| 1.11.0 | 7 / 22 | |
| 1.10.7 | 7 / 22 | |
| 1.10.6 | 7 / 22 | |
| 1.10.5 | 7 / 22 | |
| 1.10.4 | 7 / 22 | |
| 1.10.3 | 7 / 22 | |
| 1.10.2 | 7 / 22 | |
| 1.10.1 | 7 / 22 | |
| 1.10.0 | 7 / 22 | |
| 1.9.5 | 7 / 22 | |
| 1.9.4 | 7 / 22 | |
| 1.9.3 | 7 / 22 | |
| 1.9.2 | 7 / 22 | |
| 1.9.1 | 7 / 22 | |
| 1.9.0 | 7 / 22 | |
| 1.8.11 | 7 / 22 | |
| 1.8.10 | 7 / 22 | |
| 1.8.9 | 7 / 22 | |
| 1.8.8 | 7 / 22 | |
| 1.8.7 | 7 / 22 | |
| 1.8.6 | 7 / 22 | |
| 1.8.5 | 7 / 22 | |
| 1.8.4 | 7 / 22 | |
| 1.8.3 | 7 / 22 | |
| 1.8.2 | 7 / 22 | |
| 1.8.1 | 7 / 22 | |
| 1.8.0 | 7 / 22 | |
| 1.7.2 | 7 / 22 | |
| 1.7.1 | 7 / 22 | |
| 1.7.0 | 7 / 22 | |
| 1.6.0 | 7 / 22 | |
| 1.5.3 | 7 / 22 | |
| 1.5.2 | 7 / 22 | |
| 1.5.1 | 7 / 22 | |
| 1.5.0 | 7 / 22 | |
| 1.4.6 | 7 / 22 | |
| 1.4.5 | 7 / 22 | |
| 1.4.4 | 7 / 22 | |
| 1.4.3 | 7 / 22 | |
| 1.4.2 | 7 / 22 | |
| 1.4.1 | 7 / 22 | |
| 1.4.0 | 7 / 22 | |
| 1.3.3 | 7 / 22 | |
| 1.3.2 | 7 / 22 | |
| 1.3.1 | 7 / 22 | |
| 1.3.0 | 7 / 22 | |
| 1.2.1 | 7 / 22 | |
| 1.2.0 | 7 / 22 | |
| 1.1.0 | 7 / 22 | |
| 1.0.6 | 7 / 21 | |
| 1.0.4 | 7 / 21 | |
| 1.0.3 | 7 / 21 | |
| 1.0.2 | 7 / 21 | |
| 1.0.1 | 7 / 21 |
v1.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
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.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
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 (sher85) than the most recent previously approved version (steven-t-h) on 2025-01-17, but sher85 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.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.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 (steven-t-h) than the most recent previously approved version (sher85) on 2024-12-23, but steven-t-h 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.3.3
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 (sher85) than the most recent previously approved version (steven-t-h) on 2024-12-09, but sher85 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.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.