@web3auth/base
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
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 9.7.0 | 7 / 0 | |
| 9.6.0 | 7 / 0 | |
| 9.5.4 | 7 / 0 | |
| 9.5.3 | 7 / 0 | |
| 9.5.2 | 7 / 0 | |
| 9.5.1 | 7 / 0 | |
| 9.5.0 | 7 / 0 | |
| 9.4.5 | 7 / 0 | |
| 9.4.4 | 7 / 0 | |
| 9.4.3 | 7 / 0 | |
| 9.4.2 | 7 / 0 | |
| 9.4.0 | 7 / 0 | |
| 9.3.0 | 7 / 0 | |
| 9.2.3 | 7 / 0 | |
| 9.2.2 | 7 / 0 | |
| 9.2.1 | 7 / 0 | |
| 9.0.2 | 7 / 0 | |
| 9.0.1 | 7 / 0 | |
| 9.0.0 | 7 / 0 |
v9.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chaitanyapotti) than the most recent previously approved version (himanshunpm009) on 2025-02-06, but chaitanyapotti is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v9.5.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chaitanyapotti) than the most recent previously approved version (himanshunpm009) on 2025-01-20, but chaitanyapotti is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v9.5.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (himanshunpm009) than the most recent previously approved version (chaitanyapotti) on 2025-01-08, but himanshunpm009 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v9.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chaitanyapotti) than the most recent previously approved version (himanshunpm009) on 2024-12-16, but chaitanyapotti is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v9.4.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chaitanyapotti) than the most recent previously approved version (himanshunpm009) on 2024-11-29, but chaitanyapotti is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v9.4.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (himanshunpm009) than the most recent previously approved version (chaitanyapotti) on 2024-11-23, but himanshunpm009 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v9.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.