@synerise/ds-banner
Banner 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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party @synerise/ds-* package from the same trusted publisher; not a third-party supply-chain risk. | ai | |
| dependencies | unvetted-dep:@synerise/ds-icon | AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-utils | AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-tag | AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-tooltip | AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-typography | AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@synerise/ds-button | AI (dependencies): Internal sibling dep from same Synerise design system monorepo; stable pattern across all versions. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 8 / 0 | |
| 1.3.1 | 8 / 0 | |
| 1.3.0 | 8 / 0 | |
| 1.2.25 | 7 / 0 | |
| 1.2.24 | 7 / 0 | |
| 1.2.23 | 7 / 0 | |
| 1.2.22 | 7 / 0 | |
| 1.2.21 | 7 / 0 | |
| 1.2.20 | 7 / 0 | |
| 1.2.19 | 7 / 0 | |
| 1.2.18 | 7 / 0 | |
| 1.2.17 | 7 / 0 | |
| 1.2.16 | 7 / 0 | |
| 1.2.15 | 7 / 0 | |
| 1.2.14 | 7 / 0 | |
| 1.2.13 | 7 / 0 | |
| 1.2.12 | 7 / 0 | |
| 1.2.11 | 7 / 0 | |
| 1.2.10 | 7 / 0 | |
| 1.2.9 | 7 / 0 | |
| 1.2.8 | 7 / 0 | |
| 1.2.7 | 7 / 0 | |
| 1.2.6 | 7 / 0 | |
| 1.2.5 | 7 / 0 | |
| 1.2.4 | 7 / 0 | |
| 1.2.3 | 7 / 0 | |
| 1.2.2 | 7 / 0 | |
| 1.2.1 | 7 / 0 | |
| 1.2.0 | 7 / 0 | |
| 1.1.36 | 7 / 0 | |
| 1.1.35 | 7 / 0 | |
| 1.1.34 | 7 / 0 | |
| 1.1.33 | 7 / 0 | |
| 1.1.32 | 7 / 0 | |
| 1.1.31 | 7 / 0 | |
| 1.1.30 | 7 / 0 | |
| 1.1.29 | 7 / 0 | |
| 1.1.28 | 7 / 0 | |
| 1.1.27 | 7 / 0 | |
| 1.1.26 | 7 / 0 | |
| 1.1.25 | 7 / 0 | |
| 1.1.24 | 7 / 0 | |
| 1.1.23 | 7 / 0 | |
| 1.1.22 | 7 / 0 | |
| 1.1.21 | 7 / 0 | |
| 1.1.20 | 7 / 0 | |
| 1.1.19 | 7 / 0 | |
| 1.1.18 | 7 / 0 | |
| 1.1.17 | 7 / 0 | |
| 1.1.16 | 7 / 0 | |
| 1.1.15 | 7 / 0 | |
| 1.1.14 | 7 / 0 | |
| 1.1.13 | 7 / 0 | |
| 1.1.12 | 7 / 0 | |
| 1.1.11 | 7 / 0 | |
| 1.1.10 | 7 / 0 | |
| 1.1.9 | 7 / 0 | |
| 1.1.8 | 7 / 0 | |
| 1.1.7 | 7 / 0 | |
| 1.1.6 | 7 / 0 | |
| 1.1.5 | 7 / 0 | |
| 1.1.4 | 7 / 0 | |
| 1.1.3 | 7 / 0 | |
| 1.1.2 | 7 / 0 | |
| 1.1.1 | 7 / 0 | |
| 1.1.0 | 7 / 0 | |
| 1.0.0 | 7 / 0 |
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.