@dfds-ui/google-places
Components using Google places
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@dfds-ui/icons | AI (phantom-deps): Same-org sibling; may be re-exported or used transitively within the monorepo bundle. | ai | |
| phantom-deps | phantom-dep:@dfds-ui/colors | AI (phantom-deps): Same-org sibling; same rationale as @dfds-ui/icons. | ai | |
| phantom-deps | phantom-dep:@types/googlemaps | AI (phantom-deps): Type-only package; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/lodash.debounce | AI (phantom-deps): Type-only package; loaded by convention, not direct import. | ai | |
| provenance | no-provenance | AI (provenance): Large monorepo with 2593 versions; no provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 7 / 0 | |
| 3.0.0 | 7 / 0 | |
| 2.2.1 | 7 / 0 | |
| 2.0.29 | 7 / 0 | |
| 2.0.28 | 7 / 0 | |
| 2.0.27 | 7 / 0 | |
| 2.0.26 | 7 / 0 | |
| 2.0.25 | 7 / 0 | |
| 2.0.24 | 7 / 0 |
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.