@uapkg/log
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:winston | AI (phantom-deps): winston is the declared runtime dep; likely re-exported or used indirectly in the dist bundle. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Same rationale — scoped package with legitimate repo, not impersonating koa. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Same rationale — scoped package with legitimate repo, not impersonating got. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped package @uapkg/log; short name 'log' incidentally matches many popular short names. Not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same rationale — scoped package with legitimate repo, not impersonating joi. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Same rationale — scoped package with legitimate repo, not impersonating zod. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same rationale — scoped package with legitimate repo, not impersonating pg. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.9 | 1 / 0 | |
| 1.1.8 | 1 / 0 | |
| 1.1.7 | 1 / 0 | |
| 1.1.6 | 1 / 0 | |
| 0.1.2 | 1 / 0 | |
| 0.1.1 | 1 / 0 |
v1.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.