@vertigis/viewer-spec
VertiGIS Viewer Specification
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
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 61.17.0 | 0 / 27 | |
| 61.16.0 | 0 / 27 | |
| 61.15.1 | 0 / 27 | |
| 61.15.0 | 0 / 27 | |
| 61.14.1 | 0 / 23 | |
| 61.14.0 | 0 / 23 | |
| 61.13.0 | 0 / 23 | |
| 61.12.0 | 0 / 23 | |
| 61.11.0 | 0 / 23 | |
| 61.10.0 | 0 / 23 | |
| 61.9.2 | 0 / 23 | |
| 61.9.1 | 0 / 23 | |
| 61.9.0 | 0 / 23 | |
| 61.8.0 | 0 / 23 | |
| 61.7.0 | 0 / 23 | |
| 61.6.0 | 0 / 23 | |
| 61.5.0 | 0 / 23 | |
| 61.4.0 | 0 / 23 | |
| 61.3.0 | 0 / 23 | |
| 61.2.3 | 0 / 23 | |
| 61.2.2 | 0 / 23 | |
| 61.2.1 | 0 / 23 | |
| 61.2.0 | 0 / 23 | |
| 61.1.1 | 0 / 23 | |
| 61.1.0 | 0 / 23 | |
| 61.0.0 | 0 / 23 | |
| 60.9.1 | 0 / 23 | |
| 60.9.0 | 0 / 23 | |
| 60.8.1 | 0 / 23 | |
| 60.8.0 | 0 / 23 | |
| 60.7.0 | 0 / 22 | |
| 60.6.0 | 0 / 22 | |
| 60.5.1 | 0 / 22 | |
| 60.5.0 | 0 / 22 | |
| 60.4.0 | 0 / 22 | |
| 60.3.1 | 0 / 22 | |
| 60.3.0 | 0 / 22 | |
| 60.2.0 | 0 / 22 | |
| 60.1.0 | 0 / 22 | |
| 60.0.0 | 0 / 22 | |
| 59.31.0 | 0 / 22 | |
| 59.30.0 | 0 / 22 | |
| 59.29.0 | 0 / 22 | |
| 59.28.1 | 0 / 22 | |
| 59.28.0 | 0 / 22 | |
| 59.27.0 | 0 / 22 |
v61.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v61.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v60.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v59.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v59.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v59.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v59.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v59.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v59.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.