logs-gateway
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Logging gateway dynamically selects transports; pino is a core declared dep used at runtime. | ai | |
| phantom-deps | phantom-dep:consola | AI (phantom-deps): Logging transport loaded dynamically; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:pino-http | AI (phantom-deps): Logging transport loaded dynamically; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Logging transport loaded dynamically; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rotating-file-stream | AI (phantom-deps): File rotation transport loaded dynamically; stable false positive. | ai | |
| phantom-deps | phantom-dep:winston-daily-rotate-file | AI (phantom-deps): Winston transport loaded dynamically; stable false positive. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.6.0 | 15 / 10 | |
| 3.5.0 | 15 / 10 | |
| 3.2.0 | 15 / 10 | |
| 3.1.2 | 15 / 10 | |
| 3.1.1 | 15 / 10 | |
| 3.1.0 | 15 / 10 | |
| 3.0.1 | 15 / 10 | |
| 3.0.0 | 15 / 10 | |
| 2.3.0 | 15 / 10 | |
| 2.2.1 | 15 / 10 | |
| 2.2.0 | 15 / 10 | |
| 2.1.1 | 15 / 10 | |
| 2.1.0 | 15 / 10 | |
| 2.0.5 | 15 / 10 | |
| 2.0.0 | 15 / 10 | |
| 1.5.0 | 13 / 9 | |
| 1.4.1 | 13 / 9 | |
| 1.4.0 | 13 / 9 |
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.