@designliquido/mapler
Dialeto de Mapler 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Versions (showing 100 of 112)
| Version | Deps | Published |
|---|---|---|
| 0.7.10 | 2 / 14 | |
| 0.7.9 | 2 / 14 | |
| 0.7.8 | 2 / 14 | |
| 0.7.7 | 2 / 13 | |
| 0.7.6 | 2 / 13 | |
| 0.7.5 | 2 / 13 | |
| 0.7.4 | 2 / 13 | |
| 0.7.3 | 2 / 13 | |
| 0.7.2 | 2 / 13 | |
| 0.7.1 | 2 / 13 | |
| 0.7.0 | 2 / 13 | |
| 0.6.33 | 2 / 13 | |
| 0.6.32 | 2 / 13 | |
| 0.6.31 | 2 / 13 | |
| 0.6.30 | 2 / 13 | |
| 0.6.29 | 2 / 13 | |
| 0.6.28 | 2 / 13 | |
| 0.6.27 | 2 / 13 | |
| 0.6.26 | 2 / 13 | |
| 0.6.25 | 2 / 13 | |
| 0.6.24 | 2 / 13 | |
| 0.6.23 | 2 / 13 | |
| 0.6.22 | 2 / 13 | |
| 0.6.21 | 2 / 13 | |
| 0.6.20 | 2 / 13 | |
| 0.6.19 | 2 / 13 | |
| 0.6.18 | 2 / 13 | |
| 0.6.17 | 2 / 13 | |
| 0.6.16 | 2 / 13 | |
| 0.6.15 | 2 / 13 | |
| 0.6.14 | 2 / 13 | |
| 0.6.13 | 2 / 13 | |
| 0.6.12 | 2 / 13 | |
| 0.6.11 | 2 / 13 | |
| 0.6.10 | 2 / 13 | |
| 0.6.9 | 2 / 13 | |
| 0.6.8 | 2 / 13 | |
| 0.6.7 | 2 / 13 | |
| 0.6.6 | 3 / 12 | |
| 0.6.5 | 3 / 12 | |
| 0.6.4 | 3 / 12 | |
| 0.6.3 | 3 / 12 | |
| 0.6.2 | 3 / 12 | |
| 0.6.1 | 3 / 12 | |
| 0.6.0 | 3 / 12 | |
| 0.5.2 | 3 / 12 | |
| 0.5.1 | 3 / 12 | |
| 0.5.0 | 3 / 12 | |
| 0.4.5 | 3 / 12 | |
| 0.4.4 | 3 / 12 | |
| 0.4.3 | 3 / 12 | |
| 0.4.2 | 3 / 12 | |
| 0.4.1 | 3 / 12 | |
| 0.4.0 | 3 / 12 | |
| 0.3.7 | 3 / 12 | |
| 0.3.6 | 3 / 12 | |
| 0.3.5 | 3 / 12 | |
| 0.3.4 | 3 / 12 | |
| 0.3.3 | 3 / 12 | |
| 0.3.2 | 3 / 12 | |
| 0.3.1 | 3 / 12 | |
| 0.3.0 | 3 / 12 | |
| 0.2.14 | 3 / 12 | |
| 0.2.13 | 3 / 12 | |
| 0.2.12 | 3 / 12 | |
| 0.2.11 | 3 / 12 | |
| 0.2.10 | 3 / 12 | |
| 0.2.9 | 3 / 12 | |
| 0.2.8 | 3 / 12 | |
| 0.2.7 | 3 / 12 | |
| 0.2.6 | 3 / 12 | |
| 0.2.5 | 3 / 12 | |
| 0.2.4 | 3 / 12 | |
| 0.2.3 | 3 / 12 | |
| 0.2.2 | 3 / 12 | |
| 0.2.1 | 3 / 12 | |
| 0.2.0 | 3 / 12 | |
| 0.1.48 | 3 / 12 | |
| 0.1.47 | 3 / 12 | |
| 0.1.46 | 3 / 12 | |
| 0.1.45 | 3 / 12 | |
| 0.1.44 | 3 / 12 | |
| 0.1.43 | 3 / 12 | |
| 0.1.42 | 3 / 12 | |
| 0.1.41 | 3 / 12 | |
| 0.1.40 | 3 / 12 | |
| 0.1.39 | 3 / 12 | |
| 0.1.38 | 3 / 12 | |
| 0.1.37 | 3 / 12 | |
| 0.1.36 | 3 / 12 | |
| 0.1.35 | 3 / 12 | |
| 0.1.34 | 3 / 12 | |
| 0.1.33 | 3 / 12 | |
| 0.1.32 | 3 / 12 | |
| 0.1.31 | 3 / 12 | |
| 0.1.30 | 3 / 12 | |
| 0.1.29 | 3 / 12 | |
| 0.1.28 | 3 / 12 | |
| 0.1.27 | 3 / 12 | |
| 0.1.26 | 3 / 12 |
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
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.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.