@alicloud/polardb20170801
English | [简体中文](README-CN.md) 
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Alibaba Cloud SDK packages routinely add large numbers of generated API client files across versions; stable pattern for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Alibaba Cloud auto-generated SDK packages consistently lack repo/keywords; not a spam indicator for this publisher family. | ai | |
| provenance | no-provenance | AI (provenance): Alibaba Cloud SDK packages do not use Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.21.1 | 2 / 5 | |
| 6.21.0 | 2 / 5 | |
| 6.20.0 | 2 / 5 | |
| 6.19.0 | 2 / 5 | |
| 6.18.1 | 2 / 5 | |
| 6.18.0 | 2 / 5 | |
| 6.17.0 | 2 / 5 | |
| 6.16.0 | 2 / 5 | |
| 6.15.0 | 2 / 5 | |
| 6.14.1 | 2 / 5 | |
| 6.14.0 | 2 / 5 | |
| 6.13.0 | 2 / 5 | |
| 6.12.2 | 2 / 5 | |
| 6.12.1 | 2 / 5 | |
| 6.12.0 | 2 / 5 | |
| 6.11.1 | 2 / 5 | |
| 6.11.0 | 2 / 5 | |
| 6.10.5 | 2 / 5 | |
| 6.10.4 | 2 / 5 | |
| 6.10.3 | 2 / 5 | |
| 6.10.2 | 2 / 5 |
v6.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.