← Home

@checkstack/auth-credential-backend

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

enyineer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@checkstack/backend-api AI (dependencies): workspace:* dep is a monorepo-internal sibling package, not an external unvetted dependency. ai
provenance no-provenance AI (provenance): Consistent across all @checkstack/* packages; no CI provenance setup in this org. ai
npm-metadata no-description AI (npm-metadata): Internal monorepo package; missing description is expected for private workspace packages. ai
bogus-package bogus-package AI (bogus-package): Internal @checkstack monorepo package; missing metadata is consistent across the scope, not a spam/malware indicator. ai

Versions (showing 51 of 54)

View all versions
Version Deps Published
0.0.69 4 / 2
0.0.68 4 / 2
0.0.67 4 / 2
0.0.66 4 / 2
0.0.65 4 / 2
0.0.64 4 / 2
0.0.63 4 / 2
0.0.62 4 / 2
0.0.61 4 / 2
0.0.60 4 / 2
0.0.59 4 / 2
0.0.58 4 / 2
0.0.57 4 / 2
0.0.56 4 / 2
0.0.55 4 / 2
0.0.54 4 / 2
0.0.53 4 / 2
0.0.52 4 / 2
0.0.51 4 / 2
0.0.50 4 / 2
0.0.49 4 / 2
0.0.48 4 / 2
0.0.47 4 / 2
0.0.46 4 / 2
0.0.45 4 / 2
0.0.44 4 / 2
0.0.43 4 / 2
0.0.42 4 / 2
0.0.41 4 / 2
0.0.40 4 / 2
0.0.39 4 / 2
0.0.38 4 / 2
0.0.37 4 / 2
0.0.36 4 / 2
0.0.35 4 / 2
0.0.34 4 / 2
0.0.32 4 / 2
0.0.29 4 / 2
0.0.28 4 / 2
0.0.24 4 / 2
0.0.23 4 / 2
0.0.20 4 / 2
0.0.19 4 / 2
0.0.18 4 / 2
0.0.16 4 / 2
0.0.15 4 / 2
0.0.13 4 / 2
0.0.11 4 / 2
0.0.7 4 / 2
0.0.6 4 / 2
0.0.5 4 / 2

v0.0.69

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

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

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

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

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

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

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

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

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

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

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

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

1 finding
INFO No provenance attestation provenance

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