minio
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/main/IamAwsProvider.js | AI (source-diff): Babel-compiled dist output; readable IAM provider code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/IamAwsProvider.mjs | AI (source-diff): ESM build output; readable source, standard for this package's dist. | ai | |
| phantom-deps | phantom-dep:web-encoding | AI (phantom-deps): Declared runtime dep referenced indirectly; stable FP. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): minio is a well-known S3-compatible storage brand; Levenshtein proximity to pino is coincidental. | ai | |
| phantom-deps | phantom-dep:through2 | AI (phantom-deps): through2 is a declared runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 8.0.7 | 13 / 42 | |
| 8.0.6 | 14 / 42 | |
| 8.0.5 | 14 / 42 | |
| 8.0.4 | 14 / 42 | |
| 8.0.3 | 14 / 42 | |
| 8.0.2 | 14 / 42 | |
| 8.0.1 | 14 / 42 | |
| 8.0.0 | 14 / 42 |
v8.0.5
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.