← Home

@freik/helpers

npm Repository Homepage

Core set of TS/JS function helpers

15
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-utils

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Metadata gap only, no behavioral change; publisher has long clean track record. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy with unchanged content, not indicative of takeover here. ai
semgrep semgrep:new-function-constructor AI (semgrep): Fires in bun-minified bundle output; standard bundler artifact for this package. ai
phantom-deps phantom-dep:@freik/typechk AI (phantom-deps): Same-org dependency declared in package.json; phantom-dep heuristic false positive for this package. ai

Versions (showing 15 of 15)

Version Deps Published
0.5.10 1 / 9
0.5.9 1 / 9
0.5.7 1 / 9
0.5.5 1 / 9
0.5.4 1 / 9
0.5.3 1 / 9
0.5.2 1 / 9
0.4.1 1 / 9
0.4.0 1 / 9
0.3.26 1 / 9
0.3.19 1 / 9
0.3.18 1 / 9
0.3.16 1 / 9
0.3.14 1 / 10
0.3.13 1 / 15

v0.5.9

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: freik.

v0.5.4

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: freik.

v0.3.19

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: freik.

LOW No provenance attestation provenance

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

v0.3.18

1 finding
LOW No provenance attestation provenance

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

v0.3.16

1 finding
LOW No provenance attestation provenance

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

v0.3.14

1 finding
LOW No provenance attestation provenance

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

v0.3.13

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.