@designliquido/birl
Dialeto de BIRL 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 113)
| Version | Deps | Published |
|---|---|---|
| 0.6.10 | 1 / 13 | |
| 0.6.9 | 1 / 13 | |
| 0.6.8 | 1 / 13 | |
| 0.6.7 | 1 / 12 | |
| 0.6.6 | 1 / 12 | |
| 0.6.5 | 1 / 12 | |
| 0.6.4 | 1 / 12 | |
| 0.6.3 | 1 / 12 | |
| 0.6.2 | 1 / 12 | |
| 0.6.1 | 1 / 12 | |
| 0.6.0 | 1 / 12 | |
| 0.5.33 | 1 / 12 | |
| 0.5.32 | 1 / 12 | |
| 0.5.31 | 1 / 12 | |
| 0.5.30 | 1 / 12 | |
| 0.5.29 | 1 / 12 | |
| 0.5.28 | 1 / 12 | |
| 0.5.27 | 1 / 12 | |
| 0.5.26 | 1 / 12 | |
| 0.5.25 | 1 / 12 | |
| 0.5.24 | 1 / 12 | |
| 0.5.23 | 1 / 12 | |
| 0.5.22 | 1 / 12 | |
| 0.5.21 | 1 / 12 | |
| 0.5.20 | 1 / 12 | |
| 0.5.19 | 1 / 12 | |
| 0.5.18 | 1 / 12 | |
| 0.5.17 | 1 / 12 | |
| 0.5.16 | 1 / 12 | |
| 0.5.15 | 1 / 12 | |
| 0.5.14 | 1 / 12 | |
| 0.5.13 | 1 / 12 | |
| 0.5.12 | 1 / 12 | |
| 0.5.11 | 1 / 12 | |
| 0.5.10 | 1 / 12 | |
| 0.5.9 | 1 / 12 | |
| 0.5.8 | 1 / 12 | |
| 0.5.7 | 1 / 12 | |
| 0.5.6 | 1 / 12 | |
| 0.5.5 | 2 / 11 | |
| 0.5.4 | 2 / 11 | |
| 0.5.3 | 2 / 11 | |
| 0.5.2 | 2 / 11 | |
| 0.5.1 | 2 / 11 | |
| 0.5.0 | 2 / 11 | |
| 0.4.2 | 2 / 11 | |
| 0.4.1 | 2 / 11 | |
| 0.4.0 | 2 / 11 | |
| 0.3.6 | 2 / 11 | |
| 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.22 | 2 / 11 | |
| 0.2.21 | 2 / 11 | |
| 0.2.20 | 2 / 11 | |
| 0.2.19 | 2 / 11 | |
| 0.2.18 | 2 / 11 | |
| 0.2.17 | 2 / 11 | |
| 0.2.16 | 2 / 11 | |
| 0.2.15 | 2 / 11 | |
| 0.2.14 | 2 / 11 | |
| 0.2.13 | 2 / 11 | |
| 0.2.12 | 2 / 11 | |
| 0.2.11 | 2 / 11 | |
| 0.2.10 | 2 / 11 | |
| 0.2.9 | 2 / 11 | |
| 0.2.8 | 2 / 11 | |
| 0.2.7 | 2 / 11 | |
| 0.2.6 | 2 / 11 | |
| 0.2.5 | 2 / 11 | |
| 0.2.4 | 2 / 11 | |
| 0.2.3 | 2 / 11 | |
| 0.2.2 | 2 / 11 | |
| 0.2.1 | 2 / 11 | |
| 0.2.0 | 2 / 11 | |
| 0.1.47 | 2 / 11 | |
| 0.1.46 | 2 / 11 | |
| 0.1.45 | 2 / 11 | |
| 0.1.44 | 2 / 11 | |
| 0.1.43 | 2 / 11 | |
| 0.1.42 | 2 / 11 | |
| 0.1.41 | 2 / 11 | |
| 0.1.40 | 2 / 11 | |
| 0.1.39 | 2 / 11 | |
| 0.1.38 | 2 / 11 | |
| 0.1.37 | 2 / 11 | |
| 0.1.36 | 2 / 11 | |
| 0.1.35 | 2 / 11 | |
| 0.1.34 | 2 / 11 | |
| 0.1.33 | 2 / 11 | |
| 0.1.32 | 2 / 11 | |
| 0.1.31 | 2 / 11 | |
| 0.1.30 | 2 / 11 | |
| 0.1.29 | 2 / 11 | |
| 0.1.28 | 2 / 11 | |
| 0.1.27 | 2 / 11 | |
| 0.1.26 | 2 / 11 |
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.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
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.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.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.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
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. Consider requesting the maintainer enable provenance via CI/CD.
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.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.