← Home

grammy

51
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

knorpelsenf

Keywords

telegrambotapiclientframeworklibrarygrammy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-exfil-services AI (semgrep): Matches inside JSDoc comments describing Telegram file APIs; not executed code. ai

Versions (showing 51 of 90)

View all versions
Version Deps Published
1.45.1 4 / 4
1.45.0 4 / 4
1.22.4 4 / 4
1.22.3 4 / 4
1.22.2 4 / 4
1.22.1 4 / 4
1.22.0 4 / 4
1.21.2 4 / 4
1.21.1 4 / 4
1.21.0 4 / 4
1.20.4 4 / 4
1.20.3 4 / 4
1.20.2 4 / 4
1.20.1 4 / 4
1.20.0 4 / 4
1.19.3 4 / 4
1.19.2 4 / 4
1.19.1 4 / 4
1.19.0 4 / 4
1.18.3 4 / 4
1.18.2 4 / 4
1.18.1 4 / 5
1.18.0 4 / 5
1.17.2 4 / 5
1.17.1 4 / 5
1.17.0 4 / 5
1.16.2 4 / 5
1.16.1 4 / 5
1.16.0 4 / 5
1.15.3 4 / 5
1.15.2 4 / 5
1.15.1 4 / 5
1.15.0 4 / 5
1.14.1 4 / 5
1.14.0 4 / 5
1.13.1 4 / 5
1.13.0 4 / 5
1.12.5 4 / 5
1.12.4 4 / 5
1.12.3 4 / 5
1.12.2 4 / 5
1.12.1 4 / 5
1.12.0 4 / 5
1.11.2 4 / 5
1.11.1 4 / 5
1.11.0 4 / 5
1.10.1 4 / 5
1.10.0 4 / 5
1.9.2 4 / 5
1.9.1 4 / 5
1.9.0 4 / 5

v1.45.1

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.

v1.45.0

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

INFO Publisher changed: knorpelsenf → GitHub Actions (on 2026-07-16, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (knorpelsenf) on 2026-07-16, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v1.22.4

5 findings
HIGH shady-links-exfil-services: out/context.js:908 semgrep

URL pointing to known exfiltration/tunneling service (matched inside a comment — likely documentation, not executed code) Source: https://github.com/grammyjs/grammY/blob/4cb8e68d52e95f2e7de9bc3fe619b03790a5e5af/out/context.js#L908 906 | } 907 | /** > 908 | * Context-aware alias for `api.getFile`. Use this method to get basic info about a file and prepare it for download 909 | * 910 | * Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type a

HIGH shady-links-exfil-services: out/core/api.js:501 semgrep

URL pointing to known exfiltration/tunneling service (matched inside a comment — likely documentation, not executed code) Source: https://github.com/grammyjs/grammY/blob/4cb8e68d52e95f2e7de9bc3fe619b03790a5e5af/out/core/api.js#L501 499 | } 500 | /** > 501 | * Use this method to get basic info about a file and prepare it for downloading. For the moment, bots can download 502 | * 503 | * Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type a

HIGH shady-links-exfil-services: out/core/client.js:62 semgrep

URL pointing to known exfiltration/tunneling service Source: https://github.com/grammyjs/grammY/blob/4cb8e68d52e95f2e7de9bc3fe619b03790a5e5af/out/core/client.js#L62 60 | } 61 | }; > 62 | const apiRoot = (_a = options.apiRoot) !== null && _a !== void 0 ? _a : "https://api.telegram.org"; 63 | const environment = (_b = options.environment) !== null && _b !== void 0 ? _b : "prod"; 64 | this.options = {

HIGH shady-links-exfil-services: out/web.mjs:2216 semgrep

URL pointing to known exfiltration/tunneling service Source: https://github.com/grammyjs/grammY/blob/4cb8e68d52e95f2e7de9bc3fe619b03790a5e5af/out/web.mjs#L2216 2214 | } 2215 | }; > 2216 | const apiRoot = options.apiRoot ?? "https://api.telegram.org"; 2217 | const environment = options.environment ?? "prod"; 2218 | this.options = {

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

5 findings
HIGH shady-links-exfil-services: out/context.js:908 semgrep

URL pointing to known exfiltration/tunneling service (matched inside a comment — likely documentation, not executed code) Source: https://github.com/grammyjs/grammY/blob/1305c990c759c6afe706aca36209615cac936a55/out/context.js#L908 906 | } 907 | /** > 908 | * Context-aware alias for `api.getFile`. Use this method to get basic info about a file and prepare it for download 909 | * 910 | * Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type a

HIGH shady-links-exfil-services: out/core/api.js:501 semgrep

URL pointing to known exfiltration/tunneling service (matched inside a comment — likely documentation, not executed code) Source: https://github.com/grammyjs/grammY/blob/1305c990c759c6afe706aca36209615cac936a55/out/core/api.js#L501 499 | } 500 | /** > 501 | * Use this method to get basic info about a file and prepare it for downloading. For the moment, bots can download 502 | * 503 | * Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type a

HIGH shady-links-exfil-services: out/core/client.js:62 semgrep

URL pointing to known exfiltration/tunneling service Source: https://github.com/grammyjs/grammY/blob/1305c990c759c6afe706aca36209615cac936a55/out/core/client.js#L62 60 | } 61 | }; > 62 | const apiRoot = (_a = options.apiRoot) !== null && _a !== void 0 ? _a : "https://api.telegram.org"; 63 | const environment = (_b = options.environment) !== null && _b !== void 0 ? _b : "prod"; 64 | this.options = {

HIGH shady-links-exfil-services: out/web.mjs:2216 semgrep

URL pointing to known exfiltration/tunneling service Source: https://github.com/grammyjs/grammY/blob/1305c990c759c6afe706aca36209615cac936a55/out/web.mjs#L2216 2214 | } 2215 | }; > 2216 | const apiRoot = options.apiRoot ?? "https://api.telegram.org"; 2217 | const environment = options.environment ?? "prod"; 2218 | this.options = {

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

5 findings
HIGH shady-links-exfil-services: out/context.js:908 semgrep

URL pointing to known exfiltration/tunneling service (matched inside a comment — likely documentation, not executed code) Source: https://github.com/grammyjs/grammY/blob/29de76de06915bac048ba121f77215f98f2581e4/out/context.js#L908 906 | } 907 | /** > 908 | * Context-aware alias for `api.getFile`. Use this method to get basic info about a file and prepare it for download 909 | * 910 | * Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type a

HIGH shady-links-exfil-services: out/core/api.js:501 semgrep

URL pointing to known exfiltration/tunneling service (matched inside a comment — likely documentation, not executed code) Source: https://github.com/grammyjs/grammY/blob/29de76de06915bac048ba121f77215f98f2581e4/out/core/api.js#L501 499 | } 500 | /** > 501 | * Use this method to get basic info about a file and prepare it for downloading. For the moment, bots can download 502 | * 503 | * Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type a

HIGH shady-links-exfil-services: out/core/client.js:62 semgrep

URL pointing to known exfiltration/tunneling service Source: https://github.com/grammyjs/grammY/blob/29de76de06915bac048ba121f77215f98f2581e4/out/core/client.js#L62 60 | } 61 | }; > 62 | const apiRoot = (_a = options.apiRoot) !== null && _a !== void 0 ? _a : "https://api.telegram.org"; 63 | const environment = (_b = options.environment) !== null && _b !== void 0 ? _b : "prod"; 64 | this.options = {

HIGH shady-links-exfil-services: out/web.mjs:2216 semgrep

URL pointing to known exfiltration/tunneling service Source: https://github.com/grammyjs/grammY/blob/29de76de06915bac048ba121f77215f98f2581e4/out/web.mjs#L2216 2214 | } 2215 | }; > 2216 | const apiRoot = options.apiRoot ?? "https://api.telegram.org"; 2217 | const environment = options.environment ?? "prod"; 2218 | this.options = {

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

1 finding
LOW No provenance attestation provenance

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

v1.22.0

1 finding
LOW No provenance attestation provenance

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

v1.21.2

1 finding
LOW No provenance attestation provenance

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

v1.21.1

1 finding
LOW No provenance attestation provenance

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

v1.21.0

1 finding
LOW No provenance attestation provenance

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

v1.20.4

1 finding
LOW No provenance attestation provenance

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

v1.20.3

1 finding
LOW No provenance attestation provenance

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

v1.20.2

1 finding
LOW No provenance attestation provenance

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

v1.20.1

1 finding
LOW No provenance attestation provenance

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

v1.20.0

1 finding
LOW No provenance attestation provenance

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

v1.19.3

1 finding
LOW No provenance attestation provenance

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

v1.19.2

1 finding
LOW No provenance attestation provenance

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

v1.19.1

1 finding
LOW No provenance attestation provenance

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

v1.19.0

1 finding
LOW No provenance attestation provenance

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

v1.18.3

1 finding
LOW No provenance attestation provenance

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

v1.18.2

1 finding
LOW No provenance attestation provenance

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

v1.18.1

1 finding
LOW No provenance attestation provenance

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

v1.18.0

1 finding
LOW No provenance attestation provenance

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

v1.17.2

1 finding
LOW No provenance attestation provenance

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

v1.17.1

1 finding
LOW No provenance attestation provenance

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

v1.17.0

1 finding
LOW No provenance attestation provenance

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

v1.16.2

1 finding
LOW No provenance attestation provenance

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

v1.16.1

1 finding
LOW No provenance attestation provenance

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

v1.16.0

1 finding
LOW No provenance attestation provenance

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

v1.15.3

1 finding
LOW No provenance attestation provenance

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

v1.15.2

1 finding
LOW No provenance attestation provenance

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

v1.15.1

1 finding
LOW No provenance attestation provenance

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

v1.15.0

1 finding
LOW No provenance attestation provenance

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

v1.14.1

1 finding
LOW No provenance attestation provenance

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

v1.14.0

1 finding
LOW No provenance attestation provenance

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

v1.13.1

1 finding
LOW No provenance attestation provenance

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

v1.13.0

1 finding
LOW No provenance attestation provenance

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

v1.12.5

1 finding
LOW No provenance attestation provenance

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

v1.12.4

1 finding
LOW No provenance attestation provenance

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

v1.12.3

1 finding
LOW No provenance attestation provenance

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

v1.12.2

1 finding
LOW No provenance attestation provenance

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

v1.12.1

1 finding
LOW No provenance attestation provenance

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

v1.12.0

1 finding
LOW No provenance attestation provenance

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

v1.11.2

1 finding
LOW No provenance attestation provenance

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

v1.11.1

1 finding
LOW No provenance attestation provenance

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

v1.11.0

1 finding
LOW No provenance attestation provenance

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

v1.10.1

1 finding
LOW No provenance attestation provenance

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

v1.10.0

1 finding
LOW No provenance attestation provenance

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

v1.9.2

1 finding
LOW No provenance attestation provenance

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

v1.9.1

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
LOW No provenance attestation provenance

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