@swtc/lib
websocket access for jingtum blockchain
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:glob | AI (typosquat): Scoped blockchain lib is not impersonating glob; stable false positive. | ai | |
| phantom-deps | phantom-dep:@swtc/utils | AI (phantom-deps): Same-org transitive dep pulled in by @swtc/transaction or @swtc/wallet. | ai | |
| phantom-deps | phantom-dep:@swtc/keypairs | AI (phantom-deps): Same-org transitive dep; declared for re-export or peer use. | ai | |
| phantom-deps | phantom-dep:@swtc/serializer | AI (phantom-deps): Same-org transitive dep; declared for re-export or peer use. | ai | |
| phantom-deps | phantom-dep:@swtc/address-codec | AI (phantom-deps): Same-org transitive dep; declared for re-export or peer use. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 9 / 13 | |
| 1.1.2 | 11 / 15 | |
| 1.1.1 | 11 / 15 | |
| 1.1.0 | 11 / 15 | |
| 1.0.19 | 11 / 15 | |
| 1.0.18 | 11 / 15 | |
| 1.0.17 | 11 / 15 | |
| 1.0.15 | 11 / 15 | |
| 1.0.14 | 11 / 15 | |
| 1.0.13 | 11 / 15 | |
| 1.0.12 | 11 / 4 | |
| 1.0.11 | 11 / 4 | |
| 1.0.10 | 11 / 4 | |
| 1.0.8 | 11 / 4 | |
| 1.0.7 | 11 / 4 | |
| 1.0.6 | 11 / 4 | |
| 1.0.5 | 7 / 4 |
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.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.