@designliquido/portugol-studio
Dialeto de Portugol Studio 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 52 of 152)
| Version | Deps | Published |
|---|---|---|
| 0.4.29 | 4 / 12 | |
| 0.4.28 | 4 / 12 | |
| 0.4.27 | 4 / 12 | |
| 0.4.26 | 4 / 12 | |
| 0.4.25 | 4 / 12 | |
| 0.4.24 | 4 / 12 | |
| 0.4.23 | 4 / 12 | |
| 0.4.22 | 4 / 12 | |
| 0.4.21 | 4 / 12 | |
| 0.4.20 | 4 / 12 | |
| 0.4.19 | 4 / 12 | |
| 0.4.18 | 4 / 12 | |
| 0.4.17 | 4 / 12 | |
| 0.4.16 | 4 / 12 | |
| 0.4.15 | 4 / 12 | |
| 0.4.14 | 4 / 12 | |
| 0.4.13 | 4 / 12 | |
| 0.4.12 | 4 / 12 | |
| 0.4.11 | 4 / 12 | |
| 0.4.10 | 4 / 12 | |
| 0.4.9 | 4 / 12 | |
| 0.4.8 | 4 / 12 | |
| 0.4.7 | 4 / 12 | |
| 0.4.6 | 4 / 12 | |
| 0.4.5 | 4 / 12 | |
| 0.4.4 | 4 / 11 | |
| 0.4.3 | 4 / 11 | |
| 0.4.2 | 4 / 11 | |
| 0.4.1 | 4 / 11 | |
| 0.4.0 | 4 / 11 | |
| 0.3.2 | 4 / 11 | |
| 0.3.1 | 4 / 11 | |
| 0.3.0 | 4 / 11 | |
| 0.2.10 | 3 / 10 | |
| 0.2.9 | 3 / 10 | |
| 0.2.8 | 3 / 10 | |
| 0.2.7 | 3 / 10 | |
| 0.2.6 | 3 / 10 | |
| 0.2.5 | 3 / 10 | |
| 0.2.4 | 3 / 10 | |
| 0.2.3 | 3 / 10 | |
| 0.2.2 | 3 / 10 | |
| 0.2.1 | 2 / 10 | |
| 0.2.0 | 2 / 10 | |
| 0.1.4 | 1 / 10 | |
| 0.1.3 | 1 / 10 | |
| 0.1.2 | 1 / 10 | |
| 0.1.1 | 1 / 10 | |
| 0.1.0 | 1 / 10 | |
| 0.0.3 | 1 / 10 | |
| 0.0.2 | 1 / 9 | |
| 0.0.1 | 1 / 7 |
v0.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
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.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
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.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.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.