← Home

@synerise/ds-information-card

npm Repository

InformationCard UI Component for the Synerise Design System

51
Versions
ISC
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

synerise

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@synerise/ds-subtle-form AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-typography AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-description AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-card AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-icon AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-menu AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-alert AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-badge AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-avatar AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-button AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-status AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-divider AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-tooltip AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-dropdown AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-skeleton AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-copy-icon AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
dependencies unvetted-dep:@synerise/ds-scrollbar AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable FP for this package. ai
provenance no-provenance AI (provenance): Established design system package; lack of provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:@floating-ui/react AI (phantom-deps): @floating-ui/react is listed as a direct dependency in package.json; phantom-dep is a false positive here. ai

Versions (showing 51 of 78)

View all versions
Version Deps Published
1.7.0 21 / 0
1.6.20 21 / 0
1.6.19 21 / 0
1.6.18 21 / 0
1.6.17 21 / 0
1.6.16 21 / 0
1.6.15 21 / 0
1.6.14 21 / 0
1.6.13 21 / 0
1.6.12 21 / 0
1.6.11 21 / 0
1.6.10 21 / 0
1.6.9 21 / 0
1.6.8 21 / 0
1.6.7 21 / 0
1.6.6 21 / 0
1.6.5 21 / 0
1.6.4 21 / 0
1.6.3 21 / 0
1.6.2 21 / 0
1.6.1 21 / 0
1.6.0 21 / 0
1.5.9 21 / 0
1.5.8 21 / 0
1.5.7 21 / 0
1.5.6 21 / 0
1.5.5 21 / 0
1.5.4 21 / 0
1.5.3 21 / 0
1.5.2 21 / 0
1.5.1 21 / 0
1.5.0 21 / 0
1.4.1 20 / 0
1.4.0 20 / 0
1.3.9 19 / 0
1.3.8 19 / 0
1.3.7 19 / 0
1.3.6 19 / 0
1.3.5 19 / 0
1.3.4 19 / 0
1.3.3 19 / 0
1.3.2 17 / 0
1.3.1 16 / 0
1.3.0 16 / 0
1.2.3 16 / 0
1.2.2 16 / 0
1.2.1 16 / 0
1.2.0 16 / 0
1.1.8 16 / 0
1.1.7 16 / 0
1.1.6 16 / 0

v1.7.0

1 finding
INFO No provenance attestation provenance

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

v1.6.20

1 finding
INFO No provenance attestation provenance

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

v1.6.19

1 finding
INFO No provenance attestation provenance

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

v1.6.18

1 finding
INFO No provenance attestation provenance

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

v1.6.17

1 finding
INFO No provenance attestation provenance

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

v1.6.16

1 finding
INFO No provenance attestation provenance

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

v1.6.15

1 finding
INFO No provenance attestation provenance

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

v1.6.14

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.

v1.6.13

1 finding
INFO No provenance attestation provenance

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

v1.6.12

1 finding
INFO No provenance attestation provenance

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

v1.6.11

1 finding
INFO No provenance attestation provenance

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

v1.6.10

1 finding
INFO No provenance attestation provenance

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

v1.6.9

1 finding
INFO No provenance attestation provenance

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

v1.6.8

1 finding
INFO No provenance attestation provenance

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

v1.6.7

1 finding
INFO No provenance attestation provenance

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

v1.6.6

1 finding
INFO No provenance attestation provenance

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

v1.6.5

1 finding
INFO No provenance attestation provenance

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

v1.6.4

1 finding
INFO No provenance attestation provenance

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

v1.6.3

1 finding
INFO No provenance attestation provenance

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

v1.6.2

1 finding
INFO No provenance attestation provenance

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

v1.6.1

1 finding
INFO No provenance attestation provenance

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

v1.6.0

1 finding
INFO No provenance attestation provenance

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

v1.5.9

1 finding
INFO No provenance attestation provenance

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

v1.5.8

1 finding
INFO No provenance attestation provenance

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

v1.5.7

1 finding
INFO No provenance attestation provenance

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

v1.5.6

1 finding
INFO No provenance attestation provenance

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

v1.5.5

1 finding
INFO No provenance attestation provenance

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

v1.5.4

1 finding
INFO No provenance attestation provenance

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

v1.5.3

1 finding
INFO No provenance attestation provenance

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

v1.5.2

1 finding
INFO No provenance attestation provenance

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

v1.5.1

1 finding
INFO No provenance attestation provenance

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

v1.5.0

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.

v1.4.1

1 finding
INFO No provenance attestation provenance

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

v1.4.0

1 finding
INFO No provenance attestation provenance

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

v1.3.9

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.

v1.3.8

1 finding
INFO No provenance attestation provenance

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

v1.3.7

1 finding
INFO No provenance attestation provenance

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

v1.3.6

1 finding
INFO No provenance attestation provenance

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

v1.3.5

1 finding
INFO No provenance attestation provenance

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

v1.3.4

1 finding
INFO No provenance attestation provenance

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

v1.3.3

1 finding
INFO No provenance attestation provenance

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

v1.3.2

1 finding
INFO No provenance attestation provenance

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

v1.3.1

1 finding
INFO No provenance attestation provenance

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

v1.3.0

1 finding
INFO No provenance attestation provenance

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

v1.2.3

1 finding
INFO No provenance attestation provenance

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

v1.2.2

1 finding
INFO No provenance attestation provenance

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

v1.2.1

1 finding
INFO No provenance attestation provenance

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

v1.2.0

1 finding
INFO No provenance attestation provenance

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

v1.1.8

1 finding
INFO No provenance attestation provenance

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

v1.1.7

1 finding
INFO No provenance attestation provenance

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

v1.1.6

1 finding
INFO No provenance attestation provenance

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