@ideal-postcodes/address-finder
Address Finder JS library backed by the Ideal Postcodes UK address search API
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established org package with clean history; inactivity gap is not indicative of takeover given consistent publisher track record. | ai | |
| dependencies | unvetted-dep:@ideal-postcodes/jsutil | AI (dependencies): Same-org dependency from the package's own publisher; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@ideal-postcodes/core-axios | AI (dependencies): Same-org dependency from the package's own publisher; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; provenance absence is common and not a risk signal for this established package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 5.2.13 | 4 / 39 | |
| 5.2.12 | 4 / 39 | |
| 5.2.11 | 4 / 39 | |
| 5.2.6 | 4 / 35 | |
| 5.2.5 | 4 / 35 | |
| 5.2.4 | 4 / 35 | |
| 5.2.3 | 4 / 35 | |
| 5.2.2 | 4 / 35 | |
| 5.2.1 | 4 / 35 | |
| 5.2.0 | 4 / 35 | |
| 5.1.3 | 4 / 35 | |
| 5.1.0 | 4 / 35 | |
| 5.0.2 | 4 / 35 | |
| 5.0.1 | 4 / 35 | |
| 5.0.0 | 4 / 35 |
v5.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.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.