@duffel/components
Component library to build your travel product with Duffel.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@duffel/api | AI (dependencies): First-party sibling package from the same Duffel org; expected dependency for this component library. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): react is a peer dep for a React component library; not directly imported in source is expected. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer dep for a React component library; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@duffel/api | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@stripe/stripe-js | AI (phantom-deps): Stripe JS is a peer/optional dep loaded via config; phantom-dep is a stable false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Established Duffel org package; 267 versions published without provenance, consistent pattern. | ai | |
| phantom-deps | phantom-dep:date-fns-tz | AI (phantom-deps): Same bundled library pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:duration-fns | AI (phantom-deps): Same bundled library pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Bundled component library; deps referenced in config/build files, not direct imports. | ai | |
| phantom-deps | phantom-dep:@stripe/react-stripe-js | AI (phantom-deps): Same bundled library pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sentry/browser | AI (phantom-deps): Same bundled library pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:fuse.js | AI (phantom-deps): Same bundled library pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Same bundled library pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:form-data | AI (phantom-deps): Same bundled library pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:rc-slider | AI (phantom-deps): Same bundled library pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Same bundled library pattern; stable false positive. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.16.0 | 14 / 50 | |
| 3.15.0 | 14 / 50 | |
| 3.14.0 | 14 / 50 | |
| 3.13.1 | 14 / 50 | |
| 3.13.0 | 14 / 50 | |
| 3.12.4 | 14 / 50 | |
| 3.12.2 | 14 / 50 | |
| 3.12.0 | 14 / 50 | |
| 3.10.0 | 11 / 50 | |
| 3.9.1 | 11 / 50 | |
| 3.9.0 | 11 / 50 | |
| 3.8.5 | 11 / 50 | |
| 3.8.4 | 11 / 50 |
v3.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.9.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.
v3.9.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.
v3.8.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.
v3.8.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.