@swtc/api BSD-2-Clause 21 versions

@swtc/api

npm Repository Homepage

swtc lib api

21

Versions

BSD-2-Clause

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

lospringliu

Keywords

apiswtcjingtum

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@swtc/common	AI (phantom-deps): Same-org sibling package, likely re-exported.	ai	2026/07/23
phantom-deps	phantom-dep:@swtc/utils	AI (phantom-deps): Same-org sibling package, likely re-exported.	ai	2026/07/23
phantom-deps	phantom-dep:@swtc/lib	AI (phantom-deps): Same-org sibling package, likely re-exported.	ai	2026/07/23
phantom-deps	phantom-dep:@swtc/wallet	AI (phantom-deps): Same-org sibling package, likely re-exported.	ai	2026/07/23
phantom-deps	phantom-dep:@swtc/keypairs	AI (phantom-deps): Same-org sibling package, likely re-exported.	ai	2026/07/23
phantom-deps	phantom-dep:@swtc/serializer	AI (phantom-deps): Same-org sibling package, likely re-exported.	ai	2026/07/23
phantom-deps	phantom-dep:@swtc/address-codec	AI (phantom-deps): Same-org sibling package, likely re-exported.	ai	2026/07/23
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped @swtc/api is not a typosquat of unscoped 'pg'.	ai	2026/05/19
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @swtc/api is not a typosquat of unscoped 'joi'.	ai	2026/05/19
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Scoped @swtc/api is not a typosquat of unscoped 'ajv'.	ai	2026/05/19
phantom-deps	phantom-dep:webpack	AI (phantom-deps): webpack is used in build script; referenced in config, not runtime import.	ai	2026/05/19
phantom-deps	phantom-dep:webpack-cli	AI (phantom-deps): webpack-cli used via build script; config reference, not runtime import.	ai	2026/05/19
typosquat	typosquat.levenshtein:hapi	AI (typosquat): Scoped @swtc/api is not a typosquat of unscoped 'hapi'; different namespace and purpose.	ai	2026/05/19

Versions (showing 21 of 21)

Version	Deps	Published
1.2.0	11 / 8	2026-04-27
1.1.3	11 / 9	2022-09-30
1.1.2	11 / 9	2022-09-09
1.1.1	11 / 9	2022-01-11
1.1.0	11 / 9	2021-09-02
1.0.16	11 / 9	2021-08-30
1.0.15	11 / 9	2021-08-29
1.0.14	11 / 9	2021-08-17
1.0.13	11 / 9	2020-12-23
1.0.12	11 / 9	2020-09-11
1.0.11	11 / 9	2020-08-03
1.0.10	9 / 3	2020-08-01
1.0.9	9 / 3	2020-07-31
1.0.8	9 / 3	2020-07-30
1.0.7	9 / 3	2020-03-09
1.0.6	9 / 3	2020-03-01
1.0.5	9 / 3	2020-02-17
1.0.4	8 / 3	2020-02-17
1.0.2	3 / 12	2020-02-08
1.0.1	3 / 12	2020-02-07
1.0.0	2 / 12	2020-01-31

v1.1.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lospringliu.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.