← Home

@alicloud/dms-enterprise20181101

npm

English | [简体中文](README-CN.md) ![](https://aliyunsdk-pages.alicdn.com/icons/AlibabaCloud.svg)

8
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

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

jacksontianfengmk2pagecaoaliyunsdkteamconsole-fe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Alibaba Cloud SDK packages are updated in batches; long gaps between releases are normal for this publisher. ai
source-diff large-new-source-files AI (source-diff): New source files reflect expanded API coverage typical of Alibaba Cloud SDK versioning, not injected code. ai
bogus-package bogus-package AI (bogus-package): Alibaba Cloud SDK packages consistently lack repo/keywords metadata; pattern is stable across the family, not indicative of malice. ai

Versions (showing 8 of 8)

Version Deps Published
3.0.0 2 / 5
2.8.0 2 / 5
2.7.0 2 / 5
2.6.1 2 / 5
2.6.0 2 / 5
2.5.0 2 / 5
2.4.2 2 / 5
2.4.1 2 / 5

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.8.0

1 finding
LOW No provenance attestation provenance

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

v2.7.0

1 finding
LOW No provenance attestation provenance

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

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.2

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.

v2.4.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.