@byteplus/pulumi-bytepluscc MPL-2.0 21 versions

@byteplus/pulumi-bytepluscc

npm Repository Homepage

A Pulumi package to safely use byteplus Resource in Pulumi programs.

21

Versions

MPL-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

bytednpmxiujie.1chenyongjinvcloud_fexiongxiong.001wangrui.trloveyanazhenxiongtank_xieqqdxygboya1127tiebytezhangshize.fshushushuluofan.0406yanzhen.0756ash.yutiehongjichenyunfei.cshuangkaisheng.0x0wangguangbin.2022xuguoqingzhuhongshuyu

Keywords

byteplusbytepluscccategory/cloud

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:new-function-constructor	AI (semgrep): Pattern fires on Pulumi resource class constructor call, not dynamic code eval; stable false positive for this package.	ai	2026/05/03

Versions (showing 21 of 21)

Version	Deps	Published
0.0.32	1 / 3	2026-06-04
0.0.31	1 / 3	2026-06-01
0.0.30	1 / 3	2026-05-27
0.0.29	1 / 3	2026-05-27
0.0.27	1 / 3	2026-05-14
0.0.26	1 / 3	2026-05-11
0.0.25	1 / 3	2026-05-07
0.0.24	1 / 3	2026-04-23
0.0.23	1 / 3	2026-04-16
0.0.22	1 / 3	2026-04-09
0.0.17	1 / 3	2026-03-12
0.0.16	1 / 3	2026-03-09
0.0.15	1 / 3	2026-03-02
0.0.14	1 / 3	2026-02-26
0.0.13	1 / 3	2026-02-09
0.0.12	1 / 3	2026-01-22
0.0.11	1 / 3	2026-01-21
0.0.8	1 / 3	2026-01-08
0.0.7	1 / 3	2026-01-06
0.0.2	1 / 3	2025-10-31
0.0.1	1 / 3	2025-10-28

v0.0.32

1 finding

LOW No provenance attestation provenance

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

v0.0.31

1 finding

LOW No provenance attestation provenance

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

v0.0.30

1 finding

LOW No provenance attestation provenance

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

v0.0.29

1 finding

LOW No provenance attestation provenance

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

v0.0.27

1 finding

LOW No provenance attestation provenance

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

v0.0.26

1 finding

LOW No provenance attestation provenance

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

v0.0.25

1 finding

LOW No provenance attestation provenance

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

v0.0.24

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.

v0.0.23

1 finding

LOW No provenance attestation provenance

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

v0.0.22

1 finding

LOW No provenance attestation provenance

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

v0.0.17

1 finding

LOW No provenance attestation provenance

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

v0.0.16

1 finding

LOW No provenance attestation provenance

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

v0.0.15

1 finding

LOW No provenance attestation provenance

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

v0.0.14

1 finding

LOW No provenance attestation provenance

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

v0.0.13

1 finding

LOW No provenance attestation provenance

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

v0.0.12

1 finding

LOW No provenance attestation provenance

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

v0.0.11

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.

v0.0.8

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.

v0.0.7

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.

v0.0.2

1 finding

LOW No provenance attestation provenance

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

v0.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.