@canton-network/core-amulet-service
A service layer for interacting with non-token-standard Amulet operations on Canton.
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:pino | AI (phantom-deps): Library dependency re-exported or used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Library dependency re-exported or used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): Library dependency re-exported or used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:openapi-fetch | AI (phantom-deps): Library dependency re-exported or used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@canton-network/core-wallet-auth | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for re-exported types. | ai | |
| phantom-deps | phantom-dep:@canton-network/core-ledger-client | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for re-exported types. | ai | |
| phantom-deps | phantom-dep:@canton-network/core-ledger-client-types | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for re-exported types. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 11 / 8 | |
| 1.3.2 | 10 / 8 | |
| 1.3.1 | 10 / 8 | |
| 1.2.3 | 10 / 8 | |
| 1.2.2 | 10 / 8 | |
| 1.2.1 | 10 / 8 | |
| 1.2.0 | 10 / 8 | |
| 1.1.1 | 10 / 8 | |
| 1.1.0 | 10 / 8 | |
| 1.0.0 | 10 / 8 | |
| 0.10.0 | 10 / 8 | |
| 0.9.0 | 10 / 8 | |
| 0.8.0 | 10 / 11 | |
| 0.7.0 | 10 / 11 | |
| 0.6.1 | 10 / 11 | |
| 0.6.0 | 10 / 11 | |
| 0.5.0 | 10 / 11 | |
| 0.4.1 | 10 / 11 | |
| 0.4.0 | 10 / 11 | |
| 0.3.1 | 10 / 11 | |
| 0.3.0 | 10 / 11 | |
| 0.2.0 | 10 / 11 | |
| 0.1.0 | 10 / 11 |
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
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. 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
1 findingPackage 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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.