@x-developer/unified-logger
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:express | AI (phantom-deps): Express is a documented transport target; SDK exposes it via config, not a missing import. | ai | |
| phantom-deps | phantom-dep:fastify | AI (phantom-deps): Fastify is a documented transport target; SDK exposes it via config, not a missing import. | ai | |
| phantom-deps | phantom-dep:winston-papertrail | AI (phantom-deps): Papertrail is a documented transport; SDK exposes it via config, not a missing import. | ai | |
| phantom-deps | phantom-dep:@fastify/ajv-compiler | AI (phantom-deps): Fastify compiler is a documented optional dependency for schema validation. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.0.14 | 14 / 8 | |
| 1.0.12 | 14 / 8 | |
| 1.0.9 | 14 / 8 | |
| 1.0.7 | 11 / 8 | |
| 1.0.6 | 11 / 8 | |
| 1.0.5 | 11 / 8 | |
| 1.0.4 | 11 / 8 | |
| 1.0.3 | 11 / 8 | |
| 1.0.2 | 11 / 8 | |
| 1.0.1 | 11 / 8 |
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.