← Home

@botpress/api

npm
20
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

slvnperronbotpress-cloud-opsfranklevasseurmichael.massonpaul.chevilleydavid-ferland

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Intentional across @botpress/* packages; not a risk signal here. ai
bogus-package bogus-package AI (bogus-package): Botpress monorepo packages consistently lack descriptions/keywords/repo URLs; not indicative of malice. ai
source-diff encoded-string-file:dist/index.js AI (source-diff): Encoded string is the llhttp WASM binary bundled by undici; stable false positive for this package. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): @botpress/api is a scoped package in the established botpress org; Levenshtein match to 'hapi' is a false positive. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped botpress package; no relation to 'ajv'. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped botpress package; no relation to 'pg'. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped botpress package; no relation to 'joi'. ai

Versions (showing 20 of 20)

Version Deps Published
1.109.0 1 / 11
1.107.1 1 / 11
1.107.0 1 / 11
1.105.0 1 / 11
1.103.0 1 / 11
1.102.0 1 / 11
1.101.0 1 / 11
1.100.0 1 / 11
1.96.0 1 / 11
1.95.0 1 / 11
1.94.0 1 / 11
1.93.0 1 / 11
1.91.1 1 / 11
1.91.0 1 / 11
1.90.0 1 / 11
1.88.0 1 / 11
1.86.0 1 / 11
1.85.0 1 / 11
1.84.2 1 / 11
1.84.1 1 / 11

v1.109.0

1 finding
LOW No provenance attestation provenance

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

v1.107.1

1 finding
LOW No provenance attestation provenance

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

v1.107.0

1 finding
LOW No provenance attestation provenance

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

v1.105.0

1 finding
LOW No provenance attestation provenance

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

v1.103.0

1 finding
LOW No provenance attestation provenance

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

v1.102.0

1 finding
LOW No provenance attestation provenance

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

v1.101.0

1 finding
LOW No provenance attestation provenance

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

v1.100.0

2 findings
HIGH Long encoded string in modified file: dist/index.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.96.0

1 finding
LOW No provenance attestation provenance

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

v1.95.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@botpress/api' is 1 edit(s) away from popular package 'hapi'.

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.

v1.94.0

1 finding
LOW No provenance attestation provenance

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

v1.91.1

1 finding
LOW No provenance attestation provenance

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

v1.91.0

1 finding
LOW No provenance attestation provenance

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

v1.90.0

1 finding
LOW No provenance attestation provenance

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

v1.88.0

1 finding
LOW No provenance attestation provenance

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

v1.86.0

1 finding
LOW No provenance attestation provenance

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

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

v1.84.2

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.

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