← Home

@botpress/vai

npm Repository Homepage

Vitest AI (vai) – a vitest extension for testing with LLMs

42
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

slvnperronbotpress-cloud-opsfranklevasseurmichael.massonpaul.chevilleydavid-ferland

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped @botpress package; name similarity to hapi is coincidental, not a typosquat. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @botpress package; name similarity to joi is coincidental, not a typosquat. ai
phantom-deps phantom-dep:jsonrepair AI (phantom-deps): jsonrepair is a declared runtime dependency; phantom-dep heuristic misfires on bundled packages. ai

Versions (showing 42 of 42)

Version Deps Published
0.0.42 3 / 6
0.0.41 3 / 6
0.0.40 3 / 6
0.0.39 2 / 7
0.0.38 2 / 7
0.0.37 2 / 7
0.0.36 2 / 7
0.0.35 2 / 7
0.0.34 2 / 7
0.0.33 2 / 7
0.0.32 2 / 7
0.0.31 2 / 7
0.0.30 2 / 7
0.0.29 2 / 7
0.0.28 2 / 7
0.0.27 2 / 7
0.0.26 2 / 7
0.0.25 2 / 7
0.0.24 2 / 7
0.0.23 2 / 7
0.0.22 2 / 7
0.0.21 2 / 7
0.0.20 2 / 7
0.0.19 2 / 7
0.0.18 2 / 7
0.0.17 2 / 7
0.0.16 2 / 7
0.0.15 2 / 7
0.0.14 2 / 7
0.0.13 2 / 7
0.0.12 2 / 7
0.0.11 2 / 7
0.0.10 2 / 7
0.0.9 2 / 7
0.0.8 2 / 7
0.0.7 2 / 6
0.0.6 2 / 6
0.0.5 2 / 6
0.0.4 2 / 6
0.0.3 2 / 6
0.0.2 2 / 6
0.0.1 2 / 5

v0.0.42

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.41

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.40

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.39

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.38

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.37

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.36

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.5

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: slvnperron → botpress-cloud-ops (on 2024-12-30, known maintainer) provenance

This version was published by a different npm account (botpress-cloud-ops) than the most recent previously approved version (slvnperron) on 2024-12-30, but botpress-cloud-ops 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.4

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