← Home

@nimee/tests

npm

Tests common

22
Versions
ISC
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

kalitassarkis122

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): All raw-IP references are 127.0.0.1 (localhost) with env-var ports — expected for a local test-service helper package. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Scoped internal package @nimee/tests; not impersonating jest, just a test utility that depends on it. ai
phantom-deps phantom-dep:jest AI (phantom-deps): jest is a declared runtime dep used via jest config; not directly imported in source but legitimately referenced. ai
phantom-deps phantom-dep:dotenv AI (phantom-deps): dotenv loaded via config/env setup, not direct import; stable false positive for this package. ai
phantom-deps phantom-dep:ts-jest AI (phantom-deps): ts-jest is a jest transformer declared in jest config; not directly imported in source. ai
phantom-deps phantom-dep:jest-junit AI (phantom-deps): jest-junit is a jest reporter declared in config; not directly imported in source. ai

Versions (showing 22 of 22)

Version Deps Published
0.0.39 10 / 8
0.0.38 10 / 8
0.0.37 10 / 8
0.0.35 10 / 8
0.0.34 10 / 8
0.0.33 10 / 8
0.0.31 10 / 8
0.0.30 10 / 8
0.0.29 10 / 8
0.0.28 10 / 8
0.0.27 10 / 8
0.0.26 10 / 8
0.0.25 10 / 8
0.0.24 10 / 8
0.0.23 10 / 8
0.0.22 10 / 8
0.0.21 10 / 8
0.0.20 10 / 8
0.0.19 10 / 8
0.0.18 10 / 8
0.0.17 10 / 8
0.0.16 9 / 8

v0.0.31

1 finding
LOW No provenance attestation provenance

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

v0.0.30

1 finding
LOW No provenance attestation provenance

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

v0.0.29

1 finding
LOW No provenance attestation provenance

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

v0.0.28

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: shmuel_nimi → kalitas (on 2025-03-30, known maintainer) provenance

This version was published by a different npm account (kalitas) than the most recent previously approved version (shmuel_nimi) on 2025-03-30, but kalitas is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.27

1 finding
LOW No provenance attestation provenance

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

v0.0.26

1 finding
LOW No provenance attestation provenance

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

v0.0.25

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: kalitas → shmuel_nimi (on 2025-02-16, known maintainer) provenance

This version was published by a different npm account (shmuel_nimi) than the most recent previously approved version (kalitas) on 2025-02-16, but shmuel_nimi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.24

1 finding
LOW No provenance attestation provenance

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

v0.0.23

1 finding
LOW No provenance attestation provenance

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

v0.0.22

1 finding
LOW No provenance attestation provenance

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

v0.0.21

1 finding
LOW No provenance attestation provenance

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

v0.0.20

1 finding
LOW No provenance attestation provenance

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

v0.0.19

1 finding
LOW No provenance attestation provenance

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

v0.0.18

1 finding
LOW No provenance attestation provenance

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

v0.0.17

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

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.