← Home

@mesalvo/api-client

npm

Clients for Mesalvo API

14
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

matthias.wuttkemaksym.shaptalafra432pol-gubau

Keywords

mesalvotypescriptapiclient

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Consistent across all versions of this package; no other risk signals present. ai

Versions (showing 14 of 14)

Version Deps Published
0.0.42900 1 / 13
0.0.42466 1 / 13
0.0.42405 1 / 13
0.0.39627 1 / 13
0.0.39588 1 / 13
0.0.37908 1 / 13
0.0.37604 1 / 13
0.0.36780 1 / 13
0.0.35720 1 / 13
0.0.35669 1 / 13
0.0.33537 1 / 13
0.0.32412 1 / 13
0.0.32404 1 / 13
0.0.32403 1 / 13

v0.0.42900

1 finding
INFO No provenance attestation provenance

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

v0.0.42466

1 finding
INFO No provenance attestation provenance

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

v0.0.42405

1 finding
INFO No provenance attestation provenance

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

v0.0.33537

1 finding
INFO No provenance attestation provenance

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

v0.0.32412

1 finding
INFO No provenance attestation provenance

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

v0.0.32404

1 finding
INFO No provenance attestation provenance

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

v0.0.32403

1 finding
INFO No provenance attestation provenance

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