@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 — 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 |
|---|---|---|---|---|
| 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 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.21.5 | 7 / 23 | |
| 1.21.4 | 7 / 23 | |
| 1.20.0 | 7 / 23 | |
| 1.19.1 | 7 / 23 | |
| 1.18.1 | 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 |
v1.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.