@dcloudio/uni-mp-weixin
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/automator.js | AI (source-diff): Bundled minified automator tooling matching upstream repo, not true obfuscation. | ai | |
| source-diff | obfuscated-file:lib/uni.automator.js | AI (source-diff): Official automator bridge file, minified build output. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Expected for automator/devtools connection tooling. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Long-tenured trusted publisher, consistent with org's maintainer rotation. | ai |
v2.0.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (guoshengqiang) than the most recent previously approved version (fxy060608) on 2021-03-31, but guoshengqiang is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.973
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.972
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.