← Home

@stoker-platform/types

51
Versions
SEE LICENSE IN LICENSE.md
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

bigjimhere

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@fullcalendar/core AI (dependencies): @fullcalendar/core is a well-known open-source library; stable false positive for this types package. ai
bogus-package bogus-package AI (bogus-package): Internal scoped platform package; missing metadata is consistent with private org usage across 40 versions. ai
npm-metadata no-description AI (npm-metadata): Internal types package; missing description is stable pattern across versions. ai
phantom-deps phantom-dep:@google-cloud/storage AI (phantom-deps): Declared as runtime dep in a types-only package; likely re-exported or used by convention. ai
provenance no-provenance AI (provenance): No provenance is common; no other risk signals elevate this. ai

Versions (showing 51 of 73)

View all versions
Version Deps Published
0.5.64 4 / 2
0.5.63 4 / 2
0.5.62 4 / 2
0.5.61 4 / 2
0.5.60 4 / 2
0.5.59 4 / 2
0.5.58 4 / 2
0.5.57 4 / 2
0.5.56 4 / 2
0.5.55 4 / 2
0.5.54 4 / 2
0.5.53 4 / 2
0.5.52 4 / 2
0.5.51 4 / 2
0.5.50 4 / 2
0.5.49 4 / 2
0.5.48 4 / 2
0.5.47 4 / 2
0.5.46 4 / 2
0.5.45 4 / 2
0.5.44 4 / 2
0.5.43 4 / 2
0.5.42 4 / 2
0.5.41 4 / 2
0.5.40 4 / 2
0.5.39 4 / 2
0.5.38 4 / 2
0.5.37 4 / 2
0.5.36 4 / 2
0.5.35 4 / 2
0.5.34 4 / 2
0.5.33 4 / 2
0.5.32 4 / 2
0.5.31 4 / 2
0.5.30 4 / 2
0.5.29 4 / 2
0.5.28 4 / 2
0.5.27 4 / 2
0.5.26 4 / 2
0.5.25 4 / 2
0.5.24 4 / 2
0.5.23 4 / 2
0.5.22 4 / 2
0.5.21 4 / 2
0.5.20 4 / 2
0.5.19 4 / 2
0.5.18 4 / 2
0.5.17 4 / 2
0.5.16 4 / 2
0.5.15 4 / 2
0.5.14 4 / 2

v0.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.

v0.5.56

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

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

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

1 finding
INFO No provenance attestation provenance

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