telegraf
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:minimist | AI (phantom-deps): Legitimate transitive dep, no malicious use. | ai | |
| phantom-deps | phantom-dep:module-alias | AI (phantom-deps): Legitimate transitive dep, no malicious use. | ai | |
| semgrep | semgrep:shady-links-exfil-services | AI (semgrep): Match is api.telegram.org, the package's core first-party API endpoint. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get in a proxy indexer helper; standard pattern for this lib. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.16.2 | 8 / 19 | |
| 4.16.1 | 8 / 19 | |
| 4.16.0 | 8 / 19 | |
| 4.15.3 | 8 / 18 | |
| 4.15.2 | 8 / 18 | |
| 4.15.1 | 8 / 18 | |
| 4.15.0 | 8 / 18 | |
| 4.14.0 | 8 / 18 | |
| 4.13.1 | 8 / 18 | |
| 4.13.0 | 8 / 18 | |
| 4.1.1 | 8 / 21 | |
| 4.0.0 | 8 / 21 |
v4.16.2
3 findingsURL pointing to known exfiltration/tunneling service Source: ssh://[email protected]/telegraf/telegraf/blob/e881fa6fb5933dadf1a57c7261fadf79274287ee/lib/core/network/client.js#L61 59 | }; 60 | const DEFAULT_OPTIONS = { > 61 | apiRoot: 'https://api.telegram.org', 62 | apiMode: 'bot', 63 | webhookReply: true,
URL pointing to known exfiltration/tunneling service Source: ssh://[email protected]/telegraf/telegraf/blob/e881fa6fb5933dadf1a57c7261fadf79274287ee/src/core/network/client.ts#L68 66 | 67 | const DEFAULT_OPTIONS: ApiClient.Options = { > 68 | apiRoot: 'https://api.telegram.org', 69 | apiMode: 'bot', 70 | webhookReply: true,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.1
3 findingsURL pointing to known exfiltration/tunneling service Source: ssh://[email protected]/telegraf/telegraf/blob/d180036d0b058561f8d7fff4216184b38a3ab632/lib/core/network/client.js#L61 59 | }; 60 | const DEFAULT_OPTIONS = { > 61 | apiRoot: 'https://api.telegram.org', 62 | apiMode: 'bot', 63 | webhookReply: true,
URL pointing to known exfiltration/tunneling service Source: ssh://[email protected]/telegraf/telegraf/blob/d180036d0b058561f8d7fff4216184b38a3ab632/src/core/network/client.ts#L68 66 | 67 | const DEFAULT_OPTIONS: ApiClient.Options = { > 68 | apiRoot: 'https://api.telegram.org', 69 | apiMode: 'bot', 70 | webhookReply: true,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
3 findingsURL pointing to known exfiltration/tunneling service Source: ssh://[email protected]/telegraf/telegraf/blob/096dd015ad973355e9774095156f039956f96a01/lib/core/network/client.js#L61 59 | }; 60 | const DEFAULT_OPTIONS = { > 61 | apiRoot: 'https://api.telegram.org', 62 | apiMode: 'bot', 63 | webhookReply: true,
URL pointing to known exfiltration/tunneling service Source: ssh://[email protected]/telegraf/telegraf/blob/096dd015ad973355e9774095156f039956f96a01/src/core/network/client.ts#L68 66 | 67 | const DEFAULT_OPTIONS: ApiClient.Options = { > 68 | apiRoot: 'https://api.telegram.org', 69 | apiMode: 'bot', 70 | webhookReply: true,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.