@amazebird/antd-schema-table
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Org-internal package; missing description is consistent across the amazebird package family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the amazebird package family; consistent pattern, not a malware indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Org-scoped internal package; missing metadata is expected for private tooling published to npm. | ai | |
| phantom-deps | phantom-dep:resize-observer-polyfill | AI (phantom-deps): resize-observer-polyfill is a listed runtime dependency; phantom-dep heuristic false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 11 / 0 | |
| 4.0.2 | 11 / 0 | |
| 4.0.1 | 11 / 0 | |
| 3.7.0 | 11 / 0 | |
| 3.6.19 | 11 / 0 |
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.