← Home

@maxim_mazurok/gapi.client.addressvalidation-v1

npm Repository Homepage

TypeScript typings for Address Validation API v1

100
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

maxim_mazurok

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Auto-generated Google API typings; README link-dump and no keywords are structural artifacts of the generator, not spam. ai
provenance no-provenance AI (provenance): Publisher has 500 approved packages; lack of provenance is consistent across all versions and not a risk indicator here. ai
publish-pattern dormant-publish AI (publish-pattern): Automated CI/CD publishing with SLSA provenance; 342 versions published from same generator repo — dormancy likely reflects API inactivity, not takeover. ai
dependencies unvetted-dep:@types/gapi.client.discovery-v1 AI (dependencies): Framework-scoped type dependency consistent with this package's purpose; stable pattern across all versions. ai
phantom-deps phantom-dep:@types/gapi.client AI (phantom-deps): Type-only package loaded by convention; not directly imported by design. ai
phantom-deps phantom-dep:@types/gapi.client.discovery-v1 AI (phantom-deps): Type-only package loaded by convention; not directly imported by design. ai

Versions (showing 100 of 248)

Version Deps Published
0.2.20260708 2 / 0
0.2.20260707 2 / 0
0.2.20260706 2 / 0
0.2.20260705 2 / 0
0.2.20260701 2 / 0
0.2.20260630 2 / 0
0.2.20260629 2 / 0
0.2.20260628 2 / 0
0.2.20260625 2 / 0
0.2.20260622 2 / 0
0.2.20260621 2 / 0
0.2.20260617 2 / 0
0.2.20260616 2 / 0
0.2.20260614 2 / 0
0.2.20260610 2 / 0
0.2.20260609 2 / 0
0.2.20260607 2 / 0
0.2.20260604 2 / 0
0.2.20260601 2 / 0
0.2.20260531 2 / 0
0.2.20260528 2 / 0
0.2.20260526 2 / 0
0.2.20260524 2 / 0
0.2.20260520 2 / 0
0.2.20260513 2 / 0
0.2.20260511 2 / 0
0.2.20260510 2 / 0
0.2.20260506 2 / 0
0.2.20260505 2 / 0
0.2.20260504 2 / 0
0.2.20260503 2 / 0
0.2.20260429 2 / 0
0.2.20260428 2 / 0
0.2.20260427 2 / 0
0.2.20260421 2 / 0
0.2.20260413 2 / 0
0.2.20260412 2 / 0
0.1.20260407 2 / 0
0.1.20260405 2 / 0
0.1.20260329 2 / 0
0.1.20260324 2 / 0
0.1.20260316 2 / 0
0.1.20260315 2 / 0
0.1.20260302 2 / 0
0.1.20260225 2 / 0
0.1.20260216 2 / 0
0.1.20260210 2 / 0
0.1.20260203 2 / 0
0.1.20260126 2 / 0
0.1.20251210 2 / 0
0.1.20251207 2 / 0
0.1.20251109 2 / 0
0.1.20251103 2 / 0
0.1.20251102 2 / 0
0.1.20251029 2 / 0
0.1.20251022 2 / 0
0.1.20251007 2 / 0
0.1.20251001 2 / 0
0.1.20250930 2 / 0
0.1.20250921 2 / 0
0.1.20250917 2 / 0
0.1.20250909 2 / 0
0.1.20250901 2 / 0
0.1.20250819 2 / 0
0.0.20250813 2 / 0
0.0.20250812 2 / 0
0.0.20250811 2 / 0
0.0.20250721 2 / 0
0.0.20250708 2 / 0
0.0.20250630 2 / 0
0.0.20250629 2 / 0
0.0.20250623 2 / 0
0.0.20250611 2 / 0
0.0.20250604 2 / 0
0.0.20250527 2 / 0
0.0.20250514 2 / 0
0.0.20250513 2 / 0
0.0.20250512 2 / 0
0.0.20250506 2 / 0
0.0.20250427 2 / 0
0.0.20250423 2 / 0
0.0.20250422 2 / 0
0.0.20250421 2 / 0
0.0.20250420 2 / 0
0.0.20250416 2 / 0
0.0.20250415 2 / 0
0.0.20250412 2 / 0
0.0.20250409 2 / 0
0.0.20250408 2 / 0
0.0.20250407 2 / 0
0.0.20250406 2 / 0
0.0.20250402 2 / 0
0.0.20250401 2 / 0
0.0.20250331 2 / 0
0.0.20250330 2 / 0
0.0.20250326 2 / 0
0.0.20250324 2 / 0
0.0.20250323 2 / 0
0.0.20250320 2 / 0
0.0.20250317 2 / 0
Showing 100 of 248 Next page →

v0.2.20260708

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.20260707

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.20260706

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.20260705

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.20260701

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.20260630

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.20260629

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.20260628

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.20250423

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250422

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250421

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250420

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250416

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250415

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250412

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250409

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250408

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250407

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250406

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250402

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250401

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250331

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250330

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250326

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250324

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250323

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250320

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.20250317

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.