@times-components/save-and-share-bar
Save and Share bar
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established Times Components monorepo package; lack of Sigstore provenance is consistent across all versions. | ai | |
| dependencies | unvetted-dep:@times-components/utils | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@times-components/context | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@times-components/tracking | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@times-components/ts-components | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@times-components/ts-styleguide | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@times-components/user-state | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@times-components/message-bar | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on indirect usage patterns common in monorepos. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-knobs | AI (phantom-deps): Storybook config-only reference; not imported in runtime code, stable false positive for this package. | ai |
Versions (showing 76 of 276)
| Version | Deps | Published |
|---|---|---|
| 0.19.13 | 12 / 15 | |
| 0.19.12 | 12 / 15 | |
| 0.19.11 | 12 / 15 | |
| 0.19.10 | 12 / 15 | |
| 0.19.9 | 12 / 15 | |
| 0.19.8 | 12 / 15 | |
| 0.19.7 | 12 / 15 | |
| 0.19.6 | 12 / 15 | |
| 0.19.5 | 12 / 15 | |
| 0.19.4 | 12 / 15 | |
| 0.19.3 | 12 / 15 | |
| 0.19.2 | 12 / 15 | |
| 0.19.1 | 12 / 15 | |
| 0.19.0 | 12 / 15 | |
| 0.18.5 | 12 / 15 | |
| 0.18.3 | 12 / 15 | |
| 0.18.2 | 12 / 15 | |
| 0.18.1 | 12 / 15 | |
| 0.18.0 | 12 / 15 | |
| 0.17.4 | 12 / 15 | |
| 0.17.3 | 12 / 15 | |
| 0.17.2 | 12 / 15 | |
| 0.17.1 | 12 / 15 | |
| 0.17.0 | 12 / 15 | |
| 0.16.3 | 12 / 15 | |
| 0.16.2 | 12 / 15 | |
| 0.16.1 | 12 / 15 | |
| 0.16.0 | 12 / 15 | |
| 0.15.19 | 12 / 15 | |
| 0.15.18 | 12 / 15 | |
| 0.15.17 | 12 / 15 | |
| 0.15.16 | 12 / 15 | |
| 0.15.15 | 12 / 15 | |
| 0.15.14 | 12 / 15 | |
| 0.15.13 | 12 / 15 | |
| 0.15.12 | 12 / 15 | |
| 0.15.11 | 12 / 15 | |
| 0.15.10 | 12 / 15 | |
| 0.15.9 | 12 / 15 | |
| 0.15.8 | 12 / 15 | |
| 0.15.7 | 12 / 15 | |
| 0.15.6 | 12 / 15 | |
| 0.15.5 | 12 / 15 | |
| 0.15.4 | 12 / 15 | |
| 0.15.3 | 12 / 15 | |
| 0.15.2 | 12 / 15 | |
| 0.15.1 | 12 / 15 | |
| 0.15.0 | 12 / 15 | |
| 0.14.0 | 13 / 15 | |
| 0.13.9 | 12 / 15 | |
| 0.13.8 | 12 / 15 | |
| 0.13.7 | 12 / 15 | |
| 0.13.6 | 12 / 15 | |
| 0.13.5 | 12 / 15 | |
| 0.13.4 | 12 / 15 | |
| 0.13.3 | 12 / 15 | |
| 0.13.2 | 12 / 15 | |
| 0.13.1 | 12 / 15 | |
| 0.13.0 | 12 / 15 | |
| 0.12.7 | 12 / 16 | |
| 0.12.6 | 12 / 16 | |
| 0.12.5 | 12 / 16 | |
| 0.12.4 | 12 / 16 | |
| 0.12.3 | 12 / 16 | |
| 0.12.2 | 12 / 16 | |
| 0.12.1 | 12 / 16 | |
| 0.12.0 | 12 / 16 | |
| 0.11.3 | 12 / 16 | |
| 0.11.2 | 12 / 16 | |
| 0.11.1 | 12 / 16 | |
| 0.11.0 | 12 / 16 | |
| 0.10.0 | 12 / 17 | |
| 0.9.116 | 12 / 17 | |
| 0.9.115 | 12 / 17 | |
| 0.9.114 | 12 / 17 | |
| 0.9.113 | 12 / 17 |
v0.19.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.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.
v0.19.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.
v0.19.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.
v0.19.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.
v0.19.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.
v0.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.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.
v0.18.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.
v0.18.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.
v0.18.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.
v0.17.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.
v0.17.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.
v0.17.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.
v0.17.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.
v0.17.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.
v0.16.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.
v0.16.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.
v0.16.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.
v0.16.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.
v0.15.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.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.
v0.15.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.
v0.15.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.
v0.15.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.
v0.15.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.
v0.14.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.
v0.13.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.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.
v0.13.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.
v0.13.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.
v0.13.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.
v0.13.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.
v0.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.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.
v0.12.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.
v0.12.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.
v0.12.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.
v0.12.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.11.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.
v0.10.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.
v0.9.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.