@alicloud/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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Long-stable publisher history; maintainer additions predate this version, not a fresh compromise signal. | ai | |
| provenance | publisher-changed-stale | AI (provenance): 2019 publisher change, stable 2714 days on npm; not consistent with account takeover. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @alicloud package; Levenshtein match to 'got' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @alicloud package; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped @alicloud package; Levenshtein match to 'glob' is a false positive with no semantic similarity. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @alicloud package; Levenshtein match to 'zod' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @alicloud package; Levenshtein match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @alicloud package; Levenshtein match to 'koa' is a false positive. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.2.6 | 4 / 4 | |
| 1.2.5 | 4 / 4 | |
| 1.2.4 | 4 / 4 | |
| 1.2.3 | 4 / 4 | |
| 1.2.2 | 4 / 4 | |
| 1.2.1 | 4 / 3 | |
| 1.2.0 | 4 / 3 | |
| 1.1.1 | 4 / 3 | |
| 1.1.0 | 3 / 3 | |
| 1.0.0 | 3 / 3 |
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
2 findingsThis version was published by a different npm account (aliyunsdkteam) than the most recent previously approved version (jacksontian) on 2020-04-03. It has since remained available on npm for 2301 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account (hyj1991) than the most recent previously approved version (jacksontian) on 2019-02-15. It has since remained available on npm for 2714 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.