← Home

@builderbot/provider-telegram

Provider for Telegram

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

leifermendez

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/index.cjs AI (source-diff): Long hex string is a standard JPEG header constant from the telegram library, not obfuscation. ai

Versions (showing 22 of 22)

Version Deps Published
1.4.2 1 / 16
1.4.1 1 / 16
1.4.0 1 / 16
1.3.15 1 / 13
1.3.14 1 / 13
1.3.13 1 / 13
1.3.12 1 / 13
1.3.11 1 / 13
1.3.10 1 / 13
1.3.8 1 / 13
1.3.7 1 / 13
1.3.5 1 / 13
1.3.4 1 / 13
1.3.3 1 / 13
1.3.1 1 / 13
1.2.9 1 / 13
1.2.8 1 / 13
1.2.7 1 / 13
1.2.6 1 / 13
1.2.5 1 / 13
1.2.4 1 / 13
1.2.3 1 / 13

v1.2.5

1 finding
LOW No provenance attestation provenance

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

v1.2.4

1 finding
LOW No provenance attestation provenance

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

v1.2.3

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.