soap
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:koa | AI (typosquat): soap is a long-established SOAP client package, not a typosquat of koa. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used for WS-Security nonce handling, not obfuscation. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.10.0 | 8 / 28 | |
| 1.9.3 | 8 / 28 | |
| 1.9.2 | 8 / 28 | |
| 1.9.1 | 8 / 28 | |
| 1.9.0 | 8 / 28 | |
| 1.8.0 | 8 / 28 | |
| 1.7.1 | 8 / 28 | |
| 1.7.0 | 8 / 28 | |
| 1.6.5 | 11 / 29 | |
| 1.6.4 | 10 / 29 | |
| 1.6.3 | 10 / 29 | |
| 1.6.2 | 10 / 29 | |
| 1.6.1 | 10 / 29 | |
| 1.6.0 | 10 / 29 | |
| 1.5.0 | 10 / 29 | |
| 1.4.2 | 10 / 28 | |
| 1.4.1 | 10 / 26 | |
| 1.4.0 | 10 / 26 | |
| 1.3.0 | 10 / 26 | |
| 1.2.1 | 10 / 26 | |
| 1.2.0 | 10 / 26 | |
| 1.1.12 | 10 / 26 | |
| 1.1.11 | 10 / 26 | |
| 1.1.10 | 10 / 27 | |
| 1.1.9 | 10 / 27 | |
| 1.1.8 | 10 / 27 | |
| 1.1.7 | 10 / 27 | |
| 1.1.6 | 10 / 27 | |
| 1.1.5 | 10 / 27 | |
| 1.1.4 | 10 / 27 | |
| 1.1.3 | 10 / 30 | |
| 1.1.2 | 10 / 30 | |
| 1.1.1 | 10 / 31 | |
| 1.1.0 | 10 / 31 | |
| 1.0.4 | 11 / 32 | |
| 1.0.3 | 11 / 32 | |
| 1.0.2 | 11 / 32 | |
| 1.0.1 | 10 / 32 | |
| 1.0.0 | 10 / 32 |
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.