@janiscommerce/log
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped @janiscommerce package; Levenshtein match to 'glob' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @janiscommerce package; Levenshtein match to 'koa' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @janiscommerce package; Levenshtein match to 'got' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @janiscommerce package; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @janiscommerce package; Levenshtein match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @janiscommerce package; Levenshtein match to 'zod' is a false positive. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1:8585 is a localhost Lambda Layer sidecar endpoint, not exfiltration; stable pattern for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 5.5.0 | 7 / 9 | |
| 5.4.0 | 7 / 9 | |
| 5.3.0 | 7 / 9 | |
| 5.2.1 | 7 / 9 | |
| 5.2.0 | 7 / 9 | |
| 5.1.5 | 7 / 9 | |
| 5.1.4 | 7 / 9 | |
| 5.1.3 | 7 / 9 | |
| 5.1.2 | 7 / 9 | |
| 5.1.1 | 7 / 9 | |
| 5.1.0 | 7 / 9 | |
| 5.0.14 | 7 / 9 | |
| 5.0.13 | 7 / 9 | |
| 5.0.12 | 7 / 9 | |
| 5.0.11 | 7 / 9 | |
| 5.0.10 | 7 / 9 | |
| 5.0.9 | 7 / 9 | |
| 5.0.8 | 7 / 9 | |
| 5.0.7 | 6 / 9 | |
| 5.0.6 | 6 / 9 |
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.