← Home

ctrf

npm Repository Homepage
19
Versions
—
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

ctrf-io

Keywords

testtestingctrfreporterreportjsonstandardtypescriptreference-implementationtest-resultsvalidationschema

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): ctrf is the Common Test Results Format library (ctrf.io), not a typosquat of cors. Stable false positive. ai
phantom-deps phantom-dep:glob AI (phantom-deps): glob is a declared runtime dependency; phantom-dep heuristic misfires here. ai

Versions (showing 19 of 19)

Version Deps Published
0.2.0 4 / 14
0.1.0 5 / 12
0.0.17 5 / 12
0.0.16 5 / 12
0.0.15 3 / 12
0.0.14 3 / 12
0.0.13 3 / 12
0.0.12 3 / 3
0.0.11 3 / 3
0.0.10 2 / 3
0.0.9 2 / 3
0.0.8 2 / 3
0.0.7 2 / 3
0.0.6 2 / 3
0.0.5 2 / 3
0.0.4 2 / 3
0.0.3 2 / 3
0.0.2 2 / 3
0.0.1 2 / 3

v0.0.12

1 finding
LOW No provenance attestation provenance

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

v0.0.11

1 finding
LOW No provenance attestation provenance

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

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.9

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

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

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.0.1

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.