@supabase/stripe-sync-engine
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://supabase.com/ | AI (email-domain): Author field uses the Supabase homepage URL as contact, not an email address; domain hijack concern does not apply. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.48.5 | 3 / 2 | |
| 0.48.4 | 3 / 2 | |
| 0.48.3 | 3 / 2 | |
| 0.48.2 | 3 / 2 | |
| 0.48.1 | 3 / 2 | |
| 0.48.0 | 3 / 2 | |
| 0.47.0 | 3 / 2 | |
| 0.45.0 | 3 / 2 | |
| 0.44.0 | 3 / 2 | |
| 0.43.1 | 3 / 2 | |
| 0.43.0 | 3 / 2 | |
| 0.42.0 | 3 / 2 | |
| 0.41.1 | 3 / 2 | |
| 0.41.0 | 3 / 2 | |
| 0.40.2 | 3 / 2 | |
| 0.40.1 | 3 / 2 | |
| 0.40.0 | 3 / 2 | |
| 0.39.0 | 3 / 2 | |
| 0.38.1 | 3 / 2 | |
| 0.37.1 | 3 / 2 | |
| 0.36.0 | 3 / 2 | |
| 0.0.0 | 3 / 2 |
v0.48.5
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.48.4
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.48.3
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.48.2
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.48.1
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.48.0
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.47.0
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.45.0
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.0
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.1
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.1
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.2
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.1
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.1
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.1
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
2 findingsMaintainer email 'https://supabase.com/' uses domain 'https://supabase.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.