@transai/connector-runner-api-sink
This library was generated with [Nx](https://nx.dev).
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Fires only in test file (.spec.ts); standard test-env setup pattern, not a runtime concern. | ai | |
| source-diff | encoded-string-file:index.cjs | AI (source-diff): Long encoded strings are minified/bundled JS (Sentry SDK); stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package with 62 published versions; sparse metadata is consistent with a private connector module, not spam. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.36.2 | 0 / 0 | |
| 0.36.1 | 0 / 0 | |
| 0.36.0 | 0 / 0 | |
| 0.35.0 | 0 / 0 | |
| 0.34.0 | 0 / 0 | |
| 0.33.0 | 0 / 0 | |
| 0.32.0 | 0 / 0 | |
| 0.31.0 | 0 / 0 | |
| 0.30.0 | 0 / 0 | |
| 0.29.0 | 0 / 0 | |
| 0.28.0 | 0 / 0 | |
| 0.27.0 | 0 / 0 | |
| 0.26.0 | 0 / 0 | |
| 0.25.1 | 0 / 0 | |
| 0.25.0 | 0 / 0 | |
| 0.24.2 | 0 / 0 | |
| 0.24.1 | 0 / 0 | |
| 0.5.0 | 0 / 0 |
v0.36.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
2 findingsSpreading entire process.env into an object — may capture all secrets 52 | 53 | beforeEach(async () => { > 54 | process.env = { 55 | ...process.env, 56 | TRANSAI_CONFIG_SOURCE: 'api',
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.