@kb-labs/gateway-app
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@kb-labs/adapters-log-ringbuffer | AI (phantom-deps): Config-referenced optional adapter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@kb-labs/adapters-openai | AI (phantom-deps): Config-referenced optional adapter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@kb-labs/adapters-sqlite | AI (phantom-deps): Config-referenced optional adapter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@kb-labs/adapters-log-sqlite | AI (phantom-deps): Config-referenced optional adapter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@kb-labs/adapters-analytics-file | AI (phantom-deps): Config-referenced optional adapter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@kb-labs/adapters-eventbus-cache | AI (phantom-deps): Config-referenced optional adapter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@kb-labs/adapters-fs | AI (phantom-deps): Config-referenced optional adapter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@kb-labs/adapters-pino | AI (phantom-deps): Config-referenced optional adapter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@kb-labs/adapters-redis | AI (phantom-deps): Config-referenced optional adapter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@kb-labs/core-sys | AI (phantom-deps): Same-org scoped dep; monorepo pattern, stable across versions. | ai | |
| phantom-deps | phantom-dep:@fastify/websocket | AI (phantom-deps): Config-referenced dependency; stable pattern in this org's packages. | ai | |
| phantom-deps | phantom-dep:fastify-type-provider-zod | AI (phantom-deps): Config-referenced dependency; stable pattern in this org's packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is expected for non-public packages. | ai | |
| phantom-deps | phantom-dep:@fastify/swagger | AI (phantom-deps): Config-referenced dependency; stable pattern in this org's packages. | ai |
Versions (showing 51 of 71)
| Version | Deps | Published |
|---|---|---|
| 2.94.0 | 28 / 8 | |
| 2.93.0 | 28 / 8 | |
| 2.89.0 | 28 / 8 | |
| 2.88.0 | 28 / 8 | |
| 2.87.0 | 28 / 8 | |
| 2.82.0 | 28 / 8 | |
| 2.81.0 | 28 / 8 | |
| 2.80.0 | 28 / 8 | |
| 2.79.0 | 28 / 8 | |
| 2.78.0 | 28 / 8 | |
| 2.77.0 | 28 / 8 | |
| 2.75.0 | 28 / 8 | |
| 2.74.0 | 28 / 8 | |
| 2.73.0 | 28 / 8 | |
| 2.72.0 | 28 / 8 | |
| 2.69.0 | 28 / 8 | |
| 2.68.0 | 28 / 8 | |
| 2.67.0 | 28 / 8 | |
| 2.66.0 | 28 / 8 | |
| 2.65.0 | 28 / 8 | |
| 2.64.0 | 28 / 8 | |
| 2.62.0 | 28 / 8 | |
| 2.61.0 | 28 / 8 | |
| 2.60.0 | 28 / 8 | |
| 2.59.0 | 28 / 8 | |
| 2.58.0 | 28 / 8 | |
| 2.57.0 | 28 / 8 | |
| 2.56.0 | 28 / 8 | |
| 2.55.0 | 28 / 8 | |
| 2.54.0 | 28 / 8 | |
| 2.53.0 | 28 / 8 | |
| 2.47.0 | 28 / 8 | |
| 2.46.0 | 28 / 8 | |
| 2.45.0 | 28 / 8 | |
| 2.44.0 | 28 / 8 | |
| 2.43.0 | 27 / 8 | |
| 2.42.0 | 27 / 8 | |
| 2.41.0 | 27 / 8 | |
| 2.40.0 | 27 / 8 | |
| 2.39.0 | 27 / 8 | |
| 2.38.0 | 27 / 8 | |
| 2.37.0 | 27 / 8 | |
| 2.36.0 | 27 / 8 | |
| 2.35.0 | 27 / 8 | |
| 2.34.0 | 27 / 8 | |
| 2.33.0 | 27 / 8 | |
| 2.32.0 | 27 / 8 | |
| 2.31.0 | 27 / 8 | |
| 2.30.0 | 27 / 8 | |
| 2.29.0 | 27 / 8 | |
| 2.28.0 | 27 / 8 |
v2.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.