@designliquido/visualg
Dialeto de VisuAlg baseado em Delégua e TypeScript
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 48 of 148)
| Version | Deps | Published |
|---|---|---|
| 0.3.30 | 2 / 13 | |
| 0.3.29 | 2 / 13 | |
| 0.3.28 | 2 / 13 | |
| 0.3.27 | 2 / 13 | |
| 0.3.26 | 2 / 13 | |
| 0.3.25 | 2 / 13 | |
| 0.3.24 | 2 / 13 | |
| 0.3.23 | 2 / 13 | |
| 0.3.22 | 2 / 13 | |
| 0.3.21 | 2 / 13 | |
| 0.3.20 | 2 / 12 | |
| 0.3.19 | 2 / 12 | |
| 0.3.18 | 2 / 12 | |
| 0.3.17 | 2 / 12 | |
| 0.3.16 | 2 / 12 | |
| 0.3.15 | 2 / 12 | |
| 0.3.14 | 2 / 12 | |
| 0.3.13 | 2 / 12 | |
| 0.3.12 | 2 / 12 | |
| 0.3.11 | 2 / 12 | |
| 0.3.10 | 2 / 12 | |
| 0.3.9 | 2 / 12 | |
| 0.3.8 | 2 / 12 | |
| 0.3.7 | 2 / 12 | |
| 0.3.6 | 2 / 12 | |
| 0.3.5 | 2 / 11 | |
| 0.3.4 | 2 / 11 | |
| 0.3.3 | 2 / 11 | |
| 0.3.2 | 2 / 11 | |
| 0.3.1 | 2 / 11 | |
| 0.3.0 | 2 / 11 | |
| 0.2.3 | 2 / 11 | |
| 0.2.2 | 2 / 11 | |
| 0.2.1 | 2 / 11 | |
| 0.2.0 | 2 / 11 | |
| 0.1.7 | 2 / 11 | |
| 0.1.6 | 2 / 11 | |
| 0.1.5 | 2 / 11 | |
| 0.1.4 | 2 / 11 | |
| 0.1.3 | 2 / 11 | |
| 0.1.2 | 2 / 11 | |
| 0.1.1 | 2 / 11 | |
| 0.1.0 | 2 / 11 | |
| 0.0.5 | 2 / 11 | |
| 0.0.4 | 2 / 11 | |
| 0.0.3 | 2 / 11 | |
| 0.0.2 | 2 / 10 | |
| 0.0.1 | 2 / 8 |
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.