@volcengine/rdsmssql — Greenflagged

swagger client for @volcengine/rdsmssql

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

zhang6464jjjkkkaaabytednpmvcloud_fezhouykboya1127kongfanzizhangjing.2037msq17huangkaisheng.0x0zhebuchongwangrui.trgaowujianvikinglbxugaroyxuemanchi.bytedancezhujie.0kaijie_bytezhenxiongqqdxygtank_xiediyijieniguitangjinwei123songhnpamaforcexuxiaofeng.workyangaofeng.lykvtiebytexiongxiong.001shushushuluofan.0406yanzhen.0756ash.yuchenyunfei.csyuhuajian.1yunyi_6512ethan.bytewangmengyuanxuguoqingvolc-iaas-test01volc-iaasxiujie.1zhuhongshuyu

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Auto-generated SDK client in the @volcengine suite; missing metadata is typical for this package family.	ai	2026/05/15

Versions (showing 2 of 2)

Version	Deps	Published
1.0.3	1 / 2	2026-05-28
1.0.1	1 / 2	2026-01-16

v1.0.3

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: tangjinwei123 → diyijienigui (on 2026-05-28, known maintainer) provenance

This version was published by a different npm account (diyijienigui) than the most recent previously approved version (tangjinwei123) on 2026-05-28, but diyijienigui 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.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.