@quatrain/storage-supabase
Storage adapter for Supabase Storage
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes downloaded file content into a buffer for streaming; no exfiltration or code execution path. | ai | |
| phantom-deps | phantom-dep:@quatrain/core | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@supabase/supabase-js | AI (phantom-deps): Referenced in config files; phantom-dep heuristic is a false positive for this usage pattern. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.1.30 | 4 / 9 | |
| 1.1.26 | 4 / 9 | |
| 1.1.25 | 4 / 9 | |
| 1.1.24 | 4 / 9 | |
| 1.1.23 | 4 / 9 | |
| 1.1.22 | 4 / 9 | |
| 1.1.21 | 4 / 9 | |
| 1.1.20 | 4 / 9 | |
| 1.1.19 | 4 / 9 | |
| 1.1.18 | 4 / 9 | |
| 1.1.17 | 4 / 9 | |
| 1.1.16 | 4 / 9 | |
| 1.1.15 | 4 / 9 | |
| 1.1.14 | 4 / 9 | |
| 1.1.13 | 4 / 9 |
v1.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.