@mtcute/file-id
Support for TDLib and Bot API file ID for mtcute
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@fuman/utils | AI (dependencies): Same-author utility dep, low-risk addition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package with real functionality; README/keyword gaps are cosmetic. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.24.3 | 3 / 0 | |
| 0.22.0 | 3 / 0 | |
| 0.18.0 | 3 / 0 | |
| 0.17.0 | 2 / 0 | |
| 0.16.12 | 2 / 0 | |
| 0.16.9 | 2 / 0 | |
| 0.16.7 | 2 / 0 | |
| 0.16.0 | 2 / 0 | |
| 0.15.0 | 2 / 0 | |
| 0.14.0 | 2 / 0 |
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.