@synerise/ds-metric-card
MetricCard UI Component for the Synerise Design System
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Synerise DS packages consistently publish without provenance; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@synerise/ds-panel | AI (dependencies): Internal sibling package from same Synerise design system monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@synerise/ds-tooltip | AI (dependencies): Internal sibling package from same Synerise design system monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@synerise/ds-skeleton | AI (dependencies): Internal sibling package from same Synerise design system monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@synerise/ds-icon | AI (dependencies): Internal sibling package from same Synerise design system monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@synerise/ds-typography | AI (dependencies): Internal sibling package from same Synerise design system monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@synerise/ds-inline-alert | AI (dependencies): Internal sibling package from same Synerise design system monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@synerise/ds-copy-icon | AI (dependencies): Internal sibling package from same Synerise design system monorepo; stable false positive. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.2.22 | 7 / 1 | |
| 1.2.21 | 7 / 1 | |
| 1.2.20 | 7 / 1 | |
| 1.2.19 | 7 / 1 | |
| 1.2.18 | 7 / 1 | |
| 1.2.17 | 7 / 1 | |
| 1.2.16 | 7 / 1 | |
| 1.2.15 | 7 / 1 | |
| 1.2.14 | 7 / 1 | |
| 1.2.13 | 7 / 1 | |
| 1.2.12 | 7 / 1 | |
| 1.2.11 | 7 / 1 | |
| 1.2.10 | 7 / 1 | |
| 1.2.9 | 7 / 1 | |
| 1.2.8 | 7 / 1 | |
| 1.2.7 | 6 / 1 | |
| 1.2.6 | 6 / 1 | |
| 1.2.5 | 6 / 1 | |
| 1.2.4 | 6 / 1 | |
| 1.2.3 | 6 / 1 | |
| 1.2.2 | 6 / 1 | |
| 1.2.1 | 6 / 1 | |
| 1.2.0 | 6 / 1 | |
| 1.1.5 | 6 / 1 | |
| 1.1.4 | 6 / 1 | |
| 1.1.3 | 6 / 1 | |
| 1.1.2 | 6 / 1 | |
| 1.1.1 | 6 / 1 | |
| 1.1.0 | 6 / 1 |
v1.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.