@salutejs/web-telemetry
Web performance monitoring
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 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.0.19 | 2 / 11 | |
| 2.0.18 | 2 / 11 | |
| 2.0.17 | 2 / 11 | |
| 2.0.16 | 2 / 11 | |
| 2.0.15 | 2 / 11 | |
| 2.0.14 | 2 / 11 | |
| 2.0.13 | 2 / 11 | |
| 2.0.12 | 2 / 11 | |
| 2.0.11 | 2 / 11 | |
| 2.0.5 | 2 / 10 | |
| 2.0.4 | 2 / 10 | |
| 2.0.3 | 2 / 10 | |
| 2.0.2 | 2 / 10 | |
| 2.0.1 | 2 / 10 | |
| 2.0.0 | 2 / 10 |
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.