← Home

@canton-network/core-token-standard-service

npm Repository

Provides a service layer that wraps the token-standard-client and contains higher level functions for interacting with token standard contracts on Canton.

23
Versions
Apache-2.0
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

nycnewmanalexmatson-daasangeethada

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:pino AI (phantom-deps): Declared runtime dep in a service package; likely re-exported or used indirectly via config. ai
phantom-deps phantom-dep:dayjs AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this monorepo package. ai
phantom-deps phantom-dep:bignumber.js AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this monorepo package. ai
phantom-deps phantom-dep:openapi-fetch AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this monorepo package. ai
phantom-deps phantom-dep:typescript-lru-cache AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this monorepo package. ai
phantom-deps phantom-dep:@canton-network/core-splice-client AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this monorepo package. ai

Versions (showing 23 of 23)

Version Deps Published
1.4.0 13 / 8
1.3.2 13 / 8
1.3.1 13 / 8
1.2.3 13 / 8
1.2.2 13 / 8
1.2.1 13 / 8
1.2.0 13 / 8
1.1.1 13 / 8
1.1.0 13 / 8
1.0.0 13 / 8
0.10.0 13 / 8
0.9.0 13 / 8
0.8.0 13 / 11
0.7.0 13 / 11
0.6.1 13 / 11
0.6.0 13 / 11
0.5.0 13 / 11
0.4.1 13 / 11
0.4.0 13 / 11
0.3.1 13 / 11
0.3.0 13 / 11
0.2.0 12 / 11
0.1.0 12 / 11

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.2

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.2.3

1 finding
LOW No provenance attestation provenance

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

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.0

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.1

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.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.

v0.1.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.