corsair
Corsair gives you (or your agent) safe access to hundreds of integrations. It natively handles all integration plumbing. The only code you write is the code that's specific to your use case. Your data stays in your database, not a third-party service.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/oauth.js | AI (source-diff): Minified bundler output (tsup) with readable OAuth/crypto logic; not obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): kysely is a well-established TypeScript SQL query builder; its addition is consistent with the package's db/orm exports. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Package is a plugin framework actively adding API integrations; large file counts reflect new plugin modules, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth is explained by new plugin integrations (Spotify, Google Drive, etc.) with large type definition files; consistent with legitimate feature expansion. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package appears to be an internal/private framework; missing metadata is a hygiene issue but consistent across all 61 versions with no malicious indicators. | ai | |
| phantom-deps | phantom-dep:uuidv7 | AI (phantom-deps): uuidv7 is a declared runtime dependency legitimately used in the codebase; false positive. | ai | |
| dependencies | unvetted-dep:kysely-postgres-js | AI (dependencies): kysely-postgres-js is a legitimate, well-known PostgreSQL adapter for Kysely. Its addition is consistent with the package's existing kysely dependency and db/orm export paths. | ai | |
| phantom-deps | phantom-dep:kysely-postgres-js | AI (phantom-deps): kysely-postgres-js is a declared dependency for DB integration; not directly imported in library code but provided for consumers. Stable false positive. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared dependency likely used by consumers of this framework; phantom-dep finding is a stable false positive for this package. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 1 / 8 | |
| 0.1.75 | 4 / 14 | |
| 0.1.74 | 4 / 14 | |
| 0.1.73 | 4 / 14 | |
| 0.1.72 | 4 / 14 | |
| 0.1.71 | 4 / 14 | |
| 0.1.70 | 4 / 14 | |
| 0.1.69 | 4 / 14 | |
| 0.1.68 | 4 / 14 | |
| 0.1.67 | 4 / 14 | |
| 0.1.66 | 4 / 14 | |
| 0.1.65 | 4 / 14 | |
| 0.1.64 | 4 / 14 | |
| 0.1.63 | 4 / 14 | |
| 0.1.62 | 4 / 14 | |
| 0.1.61 | 4 / 14 | |
| 0.1.60 | 4 / 14 | |
| 0.1.59 | 4 / 14 | |
| 0.1.58 | 4 / 14 | |
| 0.1.57 | 4 / 15 | |
| 0.1.56 | 4 / 14 | |
| 0.1.55 | 3 / 13 | |
| 0.1.54 | 3 / 13 | |
| 0.1.53 | 3 / 13 | |
| 0.1.52 | 3 / 13 | |
| 0.1.51 | 3 / 13 | |
| 0.1.50 | 3 / 13 | |
| 0.1.49 | 3 / 13 | |
| 0.1.48 | 3 / 13 | |
| 0.1.47 | 3 / 13 | |
| 0.1.46 | 3 / 13 | |
| 0.1.45 | 3 / 13 | |
| 0.1.44 | 3 / 13 | |
| 0.1.43 | 3 / 13 | |
| 0.1.42 | 3 / 13 | |
| 0.1.41 | 3 / 13 | |
| 0.1.40 | 3 / 13 | |
| 0.1.39 | 3 / 13 | |
| 0.1.38 | 3 / 13 | |
| 0.1.37 | 3 / 13 | |
| 0.1.36 | 3 / 13 | |
| 0.1.35 | 3 / 13 | |
| 0.1.33 | 3 / 13 | |
| 0.1.32 | 3 / 13 | |
| 0.1.31 | 3 / 13 | |
| 0.1.30 | 3 / 13 | |
| 0.1.28 | 3 / 13 | |
| 0.1.27 | 3 / 13 | |
| 0.1.26 | 3 / 11 | |
| 0.1.25 | 3 / 11 | |
| 0.1.24 | 3 / 11 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.65
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.
v0.1.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.