svix
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): OpenAPI codegen expansion, benign for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Generated OpenAPI client surface; expected for this SDK. | ai | |
| source-diff | obfuscated-file:src/openapi/index.ts | AI (source-diff): Auto-generated OpenAPI re-export barrel with long lines; not obfuscation. | ai | |
| phantom-deps | phantom-dep:es6-promise | AI (phantom-deps): Polyfill loaded by convention, not direct import. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:url-parse | AI (phantom-deps): url-parse is a declared runtime dep used via config/type references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package; not directly imported by convention. Stable false positive. | ai | |
| provenance | publisher-changed | AI (provenance): Migrated to GitHub Actions CI/CD publishing with SLSA provenance; legitimate automation change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with 371 versions; dormancy gap is normal for stable SDKs. | ai |
Versions (showing 97 of 97)
| Version | Deps | Published |
|---|---|---|
| 1.99.1 | 1 / 4 | |
| 1.99.0 | 1 / 4 | |
| 1.98.0 | 1 / 4 | |
| 1.97.0 | 1 / 4 | |
| 1.96.1 | 1 / 4 | |
| 1.96.0 | 1 / 4 | |
| 1.95.2 | 1 / 4 | |
| 1.95.1 | 1 / 4 | |
| 1.95.0 | 1 / 4 | |
| 1.94.0 | 1 / 4 | |
| 1.93.0 | 1 / 4 | |
| 1.92.2 | 1 / 4 | |
| 1.91.1 | 2 / 5 | |
| 1.91.0 | 2 / 5 | |
| 1.90.0 | 2 / 5 | |
| 1.89.0 | 2 / 5 | |
| 1.88.0 | 2 / 5 | |
| 1.87.0 | 2 / 5 | |
| 1.86.0 | 2 / 5 | |
| 1.85.0 | 2 / 6 | |
| 1.84.1 | 2 / 6 | |
| 1.82.0 | 3 / 6 | |
| 1.81.0 | 3 / 6 | |
| 1.80.0 | 3 / 6 | |
| 1.79.0 | 3 / 6 | |
| 1.78.0 | 3 / 6 | |
| 1.77.0 | 3 / 6 | |
| 1.76.1 | 6 / 13 | |
| 1.76.0 | 6 / 13 | |
| 1.75.1 | 6 / 13 | |
| 1.75.0 | 6 / 13 | |
| 1.74.1 | 6 / 13 | |
| 1.74.0 | 6 / 13 | |
| 1.73.0 | 6 / 13 | |
| 1.72.0 | 6 / 13 | |
| 1.71.0 | 7 / 13 | |
| 1.70.1 | 7 / 13 | |
| 1.70.0 | 7 / 13 | |
| 1.69.0 | 7 / 13 | |
| 1.68.0 | 7 / 13 | |
| 1.67.0 | 6 / 12 | |
| 1.66.0 | 6 / 12 | |
| 1.65.0 | 6 / 12 | |
| 1.64.1 | 6 / 12 | |
| 1.64.0 | 6 / 12 | |
| 1.63.1 | 6 / 12 | |
| 1.63.0 | 6 / 12 | |
| 1.62.0 | 6 / 12 | |
| 1.61.4 | 6 / 12 | |
| 1.61.3 | 6 / 12 | |
| 1.61.2 | 6 / 12 | |
| 1.61.1 | 6 / 12 | |
| 1.61.0 | 6 / 12 | |
| 1.60.1 | 6 / 12 | |
| 1.60.0 | 6 / 12 | |
| 1.59.2 | 6 / 12 | |
| 1.59.1 | 6 / 12 | |
| 1.59.0 | 6 / 12 | |
| 1.42.0 | 6 / 11 | |
| 1.39.0 | 6 / 11 | |
| 1.37.0 | 5 / 10 | |
| 1.36.0 | 5 / 10 | |
| 1.35.0 | 5 / 10 | |
| 1.34.0 | 5 / 10 | |
| 1.33.0 | 5 / 10 | |
| 1.32.0 | 5 / 10 | |
| 1.31.0 | 5 / 10 | |
| 1.30.0 | 5 / 10 | |
| 1.29.0 | 5 / 10 | |
| 1.28.0 | 5 / 10 | |
| 1.27.0 | 5 / 10 | |
| 1.26.0 | 5 / 10 | |
| 1.25.0 | 5 / 10 | |
| 1.24.0 | 5 / 10 | |
| 1.23.0 | 5 / 10 | |
| 1.22.0 | 5 / 10 | |
| 1.21.0 | 5 / 10 | |
| 1.20.0 | 5 / 10 | |
| 1.19.0 | 5 / 10 | |
| 1.18.0 | 5 / 10 | |
| 1.17.0 | 5 / 10 | |
| 1.16.0 | 5 / 10 | |
| 1.15.0 | 5 / 10 | |
| 1.14.0 | 5 / 10 | |
| 1.13.0 | 5 / 10 | |
| 1.12.0 | 5 / 10 | |
| 1.11.0 | 5 / 10 | |
| 1.10.0 | 5 / 10 | |
| 1.9.0 | 5 / 10 | |
| 1.8.1 | 5 / 10 | |
| 1.8.0 | 5 / 10 | |
| 1.7.0 | 5 / 10 | |
| 1.6.0 | 5 / 10 | |
| 1.5.2 | 5 / 10 | |
| 1.5.1 | 5 / 10 | |
| 1.5.0 | 5 / 10 | |
| 1.4.12 | 5 / 10 |
v1.99.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.99.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.98.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.97.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.64.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
2 findingsNewly 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.
v1.39.0
2 findingsNewly 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.
v1.37.0
2 findingsNewly 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.
v1.36.0
2 findingsNewly 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.
v1.35.0
2 findingsNewly 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.
v1.34.0
2 findingsNewly 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.
v1.33.0
2 findingsNewly 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.
v1.32.0
2 findingsNewly 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.
v1.31.0
2 findingsNewly 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.
v1.30.0
2 findingsNewly 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.
v1.29.0
2 findingsNewly 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.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.