← Home

@rivetkit/traces

npm

Generic tracing storage and OTLP export for RivetKit

24
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

nathanflurryanticipate-brave-cookies

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Common for this ecosystem; no other risk signals present. ai

Versions (showing 24 of 24)

Version Deps Published
2.3.10 4 / 7
2.3.9 4 / 7
2.3.8 4 / 7
2.3.7 4 / 7
2.3.6 4 / 7
2.3.5 4 / 7
2.3.4 4 / 7
2.3.3 4 / 7
2.3.2 4 / 7
2.3.1 4 / 7
2.3.0 4 / 7
2.2.1 4 / 7
2.2.0 4 / 7
2.1.10 4 / 7
2.1.9 4 / 7
2.1.8 4 / 7
2.1.7 4 / 7
2.1.6 4 / 7
2.1.5 4 / 7
2.1.4 4 / 7
2.1.3 4 / 7
2.1.2 4 / 7
2.1.1 4 / 7
2.1.0 4 / 7

v2.3.10

1 finding
INFO No provenance attestation provenance

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

v2.3.9

1 finding
INFO No provenance attestation provenance

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

v2.3.8

1 finding
INFO No provenance attestation provenance

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

v2.3.7

1 finding
INFO No provenance attestation provenance

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

v2.3.6

1 finding
INFO No provenance attestation provenance

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

v2.3.5

1 finding
INFO No provenance attestation provenance

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

v2.3.4

1 finding
INFO No provenance attestation provenance

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

v2.3.3

1 finding
INFO No provenance attestation provenance

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