@quatrain/cloudwrapper-supabase
Cloud Wrapper adapter for Supabase
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:api-obfuscation-reflect | AI (semgrep): Reflect.get() used for a simple eventMap enum lookup in SupabaseCloudWrapper.ts — not obfuscation. | ai | |
| phantom-deps | phantom-dep:@quatrain/core | AI (phantom-deps): Same-org peer dependency; declared in both peerDependencies and dependencies, phantom-dep is a false positive here. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.2.2 | 6 / 11 | |
| 1.2.1 | 6 / 11 | |
| 1.1.36 | 6 / 11 | |
| 1.1.35 | 6 / 11 | |
| 1.1.34 | 6 / 11 | |
| 1.1.33 | 6 / 11 | |
| 1.1.32 | 6 / 11 | |
| 1.1.31 | 6 / 11 | |
| 1.1.30 | 6 / 11 | |
| 1.1.29 | 6 / 11 | |
| 1.1.28 | 6 / 11 | |
| 1.1.27 | 6 / 11 | |
| 1.1.26 | 6 / 11 | |
| 1.1.25 | 6 / 11 | |
| 1.1.24 | 6 / 11 | |
| 1.1.23 | 4 / 11 | |
| 1.1.22 | 4 / 11 | |
| 1.1.21 | 3 / 10 | |
| 1.1.20 | 3 / 10 | |
| 1.1.19 | 3 / 10 | |
| 1.1.18 | 3 / 10 | |
| 1.1.17 | 3 / 10 | |
| 1.1.16 | 4 / 10 |
v1.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.