@likec4/log
Shared interface for logging
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI is expected for this monorepo; SLSA attestation confirms integrity. | ai | |
| phantom-deps | phantom-dep:std-env | AI (phantom-deps): Analyzer notes it's referenced in config files; not a true phantom dep for this package. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @likec4 package; false positive from suffix comparison. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @likec4 package; false positive from suffix comparison. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped @likec4 package; Levenshtein match on suffix 'log' vs 'glob' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @likec4 package; false positive from suffix comparison. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @likec4 package; false positive from suffix comparison. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @likec4 package; false positive from suffix comparison. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 1.59.2 | 1 / 8 | |
| 1.59.1 | 1 / 8 | |
| 1.59.0 | 1 / 8 | |
| 1.58.0 | 1 / 8 | |
| 1.57.0 | 1 / 8 | |
| 1.56.0 | 1 / 8 | |
| 1.55.1 | 1 / 8 | |
| 1.55.0 | 1 / 8 | |
| 1.54.0 | 1 / 8 | |
| 1.53.0 | 1 / 8 | |
| 1.52.0 | 0 / 9 | |
| 1.51.0 | 0 / 9 | |
| 1.50.0 | 1 / 8 | |
| 1.49.0 | 1 / 8 | |
| 1.48.0 | 2 / 8 | |
| 1.46.1 | 1 / 9 | |
| 1.46.0 | 1 / 9 | |
| 1.45.0 | 1 / 9 | |
| 1.44.0 | 1 / 9 | |
| 1.43.0 | 1 / 9 | |
| 1.42.1 | 1 / 9 | |
| 1.42.0 | 1 / 9 | |
| 1.41.0 | 1 / 8 | |
| 1.40.0 | 1 / 8 | |
| 1.39.5 | 1 / 8 | |
| 1.39.4 | 1 / 8 | |
| 1.39.3 | 1 / 8 | |
| 1.39.2 | 1 / 8 | |
| 1.39.1 | 1 / 8 | |
| 1.39.0 | 1 / 8 | |
| 1.38.1 | 1 / 8 | |
| 1.38.0 | 1 / 8 | |
| 1.37.0 | 1 / 8 | |
| 1.36.1 | 1 / 8 | |
| 1.36.0 | 1 / 8 | |
| 1.35.0 | 1 / 8 | |
| 1.34.2 | 1 / 8 | |
| 1.34.1 | 1 / 8 | |
| 1.34.0 | 1 / 8 | |
| 1.33.0 | 1 / 8 | |
| 1.32.2 | 1 / 8 | |
| 1.32.1 | 1 / 8 | |
| 1.32.0 | 1 / 8 | |
| 1.31.0 | 1 / 8 | |
| 1.22.1 | 1 / 9 | |
| 1.22.0 | 1 / 9 | |
| 1.10.1 | 0 / 5 | |
| 1.10.0 | 0 / 5 | |
| 1.9.0 | 0 / 5 | |
| 1.8.1 | 1 / 4 | |
| 1.8.0 | 1 / 4 | |
| 1.7.4 | 1 / 4 | |
| 1.7.3 | 1 / 4 | |
| 1.7.2 | 1 / 4 | |
| 1.7.1 | 1 / 4 |
v1.59.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.59.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.59.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.