@aws-amplify/geo
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped AWS Amplify package; 'geo' vs 'glob' match is a coincidental substring, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped AWS Amplify package; 'geo' vs 'got' match is a coincidental substring, not impersonation. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 3.0.94 | 5 / 1 | |
| 3.0.93 | 5 / 1 | |
| 3.0.92 | 5 / 1 | |
| 3.0.91 | 5 / 1 | |
| 3.0.90 | 5 / 1 | |
| 3.0.89 | 5 / 1 | |
| 3.0.88 | 5 / 1 | |
| 3.0.87 | 5 / 1 | |
| 3.0.86 | 5 / 1 | |
| 3.0.85 | 5 / 1 | |
| 3.0.84 | 5 / 1 | |
| 3.0.83 | 5 / 1 | |
| 3.0.82 | 5 / 1 | |
| 3.0.81 | 5 / 1 | |
| 3.0.80 | 5 / 2 | |
| 3.0.79 | 5 / 2 | |
| 3.0.78 | 5 / 2 | |
| 3.0.77 | 5 / 2 | |
| 3.0.76 | 5 / 2 | |
| 3.0.75 | 5 / 2 | |
| 3.0.74 | 5 / 2 | |
| 3.0.73 | 5 / 2 | |
| 3.0.72 | 5 / 2 | |
| 3.0.71 | 5 / 2 | |
| 3.0.70 | 5 / 2 | |
| 3.0.69 | 5 / 2 | |
| 3.0.68 | 5 / 2 | |
| 3.0.67 | 4 / 2 | |
| 3.0.66 | 4 / 2 | |
| 3.0.65 | 4 / 2 | |
| 3.0.64 | 4 / 2 | |
| 3.0.63 | 4 / 2 | |
| 3.0.62 | 4 / 2 | |
| 3.0.61 | 4 / 2 | |
| 3.0.60 | 4 / 2 | |
| 3.0.59 | 4 / 2 | |
| 3.0.58 | 4 / 2 | |
| 3.0.57 | 4 / 2 | |
| 3.0.56 | 4 / 2 | |
| 3.0.55 | 4 / 2 | |
| 3.0.54 | 4 / 2 | |
| 3.0.53 | 4 / 2 | |
| 3.0.52 | 4 / 2 | |
| 3.0.51 | 4 / 2 | |
| 3.0.50 | 4 / 2 | |
| 3.0.49 | 4 / 2 | |
| 3.0.48 | 4 / 2 | |
| 3.0.47 | 4 / 2 | |
| 3.0.46 | 4 / 2 | |
| 3.0.45 | 4 / 2 | |
| 3.0.44 | 4 / 2 |
v3.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.