← Home

@freik/typechk

npm Repository Homepage

Core set of TS/JS type checking helpers

24
Versions
Unlicense
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

freik

Keywords

js-utilstypestypechecktypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): Fires in minified bundler output; not dynamic user-input execution. Stable false positive for this package. ai

Versions (showing 24 of 24)

Version Deps Published
0.9.6 0 / 10
0.9.5 0 / 10
0.9.3 0 / 10
0.9.2 0 / 10
0.9.1 0 / 10
0.9.0 0 / 10
0.8.4 0 / 10
0.8.3 0 / 10
0.8.2 0 / 10
0.8.1 0 / 10
0.7.1 0 / 10
0.7.0 0 / 10
0.6.14 0 / 10
0.6.13 0 / 10
0.6.11 0 / 10
0.6.10 0 / 10
0.6.9 0 / 10
0.6.8 0 / 10
0.6.6 0 / 10
0.6.4 0 / 10
0.6.2 0 / 10
0.6.1 0 / 11
0.6.0 0 / 11
0.5.12 0 / 16

v0.6.6

1 finding
LOW No provenance attestation provenance

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

v0.6.4

1 finding
LOW No provenance attestation provenance

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

v0.6.2

1 finding
LOW No provenance attestation provenance

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

v0.6.1

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.12

1 finding
LOW No provenance attestation provenance

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