surge-sdk
JavaScript SDK for surge.sh
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:node-fetch | AI (phantom-deps): node-fetch is a legitimate, well-known HTTP library; its presence as a declared-but-not-directly-imported dep is a minor code hygiene issue, not a security risk. | ai | |
| provenance | missing-githead | AI (provenance): Publisher sintaxi has a strong track record (236 approved, 0 rejected). Missing gitHead is likely a publish environment change, not a supply chain indicator for this package. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): The `request` library is a well-known, widely-used HTTP client. Its use is expected and appropriate for an HTTP-based SDK like surge-sdk. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package is 2247 days old with a trusted publisher track record. Lack of Sigstore provenance is expected for packages predating that tooling. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): The new Function usage is a static default HTTP status handler in a config merge pattern — not processing untrusted input. Stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established SDK for surge.sh with legitimate repo and author. Sparse README/no keywords are cosmetic, not security signals. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.10.1 | 1 / 0 | |
| 0.10.0 | 1 / 0 | |
| 0.9.0 | 1 / 0 | |
| 0.8.0 | 1 / 0 | |
| 0.7.0 | 1 / 0 | |
| 0.6.4 | 1 / 0 | |
| 0.6.3 | 1 / 0 | |
| 0.6.2 | 1 / 0 | |
| 0.6.1 | 1 / 0 | |
| 0.6.0 | 1 / 0 | |
| 0.5.2 | 1 / 0 | |
| 0.5.1 | 1 / 2 | |
| 0.5.0 | 1 / 2 | |
| 0.4.0 | 8 / 2 | |
| 0.3.2 | 6 / 2 | |
| 0.3.1 | 6 / 2 | |
| 0.3.0 | 6 / 2 | |
| 0.2.4 | 6 / 2 | |
| 0.2.3 | 6 / 2 | |
| 0.2.2 | 6 / 2 | |
| 0.1.2 | 6 / 2 | |
| 0.1.1 | 6 / 2 |
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sintaxi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sintaxi.
v0.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sintaxi.
v0.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sintaxi.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.