← Home

@meistrari/usage

TypeScript SDK for emitting usage events to the usage-api service.

27
Versions
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

prxg220xthierrylucassiqueira08rjmunhozamorim33henrykunhrodrigo_lgczaghiianfiremanmatheusvellonethullyocunharenanllm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Publisher has 36 approved packages in the same org; 0.0.0 reflects org versioning convention, not malicious intent. ai

Versions (showing 27 of 27)

Version Deps Published
1.21.0 1 / 6
1.20.0 1 / 6
1.19.1 1 / 6
1.19.0 1 / 6
1.18.0 1 / 6
1.17.0 1 / 6
1.16.0 1 / 6
1.15.0 1 / 6
1.14.0 1 / 6
1.13.1 1 / 6
1.13.0 1 / 6
1.12.0 1 / 6
1.11.0 1 / 6
1.10.1 1 / 6
1.10.0 1 / 6
1.9.1 1 / 6
1.9.0 1 / 6
1.8.0 1 / 6
1.7.0 1 / 6
1.6.0 1 / 6
1.5.0 1 / 6
1.4.0 1 / 6
1.3.0 1 / 6
1.2.0 1 / 6
1.1.0 1 / 6
1.0.0 1 / 6
0.0.0 1 / 6

v1.21.0

1 finding
LOW No provenance attestation provenance

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

v1.20.0

1 finding
LOW No provenance attestation provenance

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

v1.19.1

1 finding
LOW No provenance attestation provenance

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

v1.19.0

1 finding
LOW No provenance attestation provenance

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