@xapp/stentor-app
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 100 of 154)
| Version | Deps | Published |
|---|---|---|
| 1.85.1 | 0 / 11 | |
| 1.80.3 | 0 / 11 | |
| 1.78.2 | 0 / 11 | |
| 1.78.0 | 0 / 11 | |
| 1.77.2 | 0 / 11 | |
| 1.76.22 | 0 / 11 | |
| 1.76.20 | 0 / 11 | |
| 1.76.16 | 0 / 11 | |
| 1.76.10 | 0 / 11 | |
| 1.76.9 | 0 / 11 | |
| 1.76.6 | 0 / 11 | |
| 1.76.5 | 0 / 11 | |
| 1.76.4 | 0 / 11 | |
| 1.76.1 | 0 / 11 | |
| 1.74.23 | 0 / 11 | |
| 1.74.22 | 0 / 11 | |
| 1.74.18 | 0 / 11 | |
| 1.74.9 | 0 / 11 | |
| 1.73.19 | 0 / 11 | |
| 1.73.11 | 0 / 11 | |
| 1.73.6 | 0 / 11 | |
| 1.72.11 | 0 / 11 | |
| 1.72.8 | 0 / 11 | |
| 1.72.7 | 0 / 11 | |
| 1.72.4 | 0 / 11 | |
| 1.72.3 | 0 / 11 | |
| 1.71.29 | 0 / 11 | |
| 1.71.27 | 0 / 11 | |
| 1.71.24 | 0 / 11 | |
| 1.71.23 | 0 / 11 | |
| 1.71.21 | 0 / 11 | |
| 1.71.18 | 0 / 11 | |
| 1.71.12 | 0 / 11 | |
| 1.71.11 | 0 / 11 | |
| 1.71.9 | 0 / 11 | |
| 1.71.8 | 0 / 11 | |
| 1.71.4 | 0 / 11 | |
| 1.71.1 | 0 / 11 | |
| 1.70.50 | 0 / 11 | |
| 1.70.49 | 0 / 11 | |
| 1.70.47 | 0 / 11 | |
| 1.70.46 | 0 / 11 | |
| 1.70.44 | 0 / 11 | |
| 1.70.35 | 0 / 11 | |
| 1.70.31 | 0 / 11 | |
| 1.70.19 | 0 / 11 | |
| 1.70.18 | 0 / 11 | |
| 1.70.16 | 0 / 11 | |
| 1.70.9 | 0 / 11 | |
| 1.70.8 | 0 / 11 | |
| 1.70.6 | 0 / 11 | |
| 1.70.3 | 0 / 11 | |
| 1.69.4 | 0 / 11 | |
| 1.69.2 | 0 / 11 | |
| 1.69.1 | 0 / 11 | |
| 1.69.0 | 0 / 11 | |
| 1.68.1 | 0 / 11 | |
| 1.66.10 | 0 / 11 | |
| 1.66.9 | 0 / 11 | |
| 1.66.8 | 0 / 11 | |
| 1.66.6 | 0 / 11 | |
| 1.66.0 | 0 / 11 | |
| 1.65.43 | 0 / 11 | |
| 1.65.41 | 0 / 11 | |
| 1.65.40 | 0 / 11 | |
| 1.65.38 | 0 / 11 | |
| 1.65.35 | 0 / 11 | |
| 1.65.34 | 0 / 11 | |
| 1.65.33 | 0 / 11 | |
| 1.65.31 | 0 / 11 | |
| 1.65.29 | 0 / 11 | |
| 1.65.28 | 0 / 11 | |
| 1.65.27 | 0 / 11 | |
| 1.65.26 | 0 / 11 | |
| 1.65.21 | 0 / 11 | |
| 1.65.20 | 0 / 11 | |
| 1.65.16 | 0 / 11 | |
| 1.65.11 | 0 / 11 | |
| 1.65.10 | 0 / 11 | |
| 1.65.8 | 0 / 11 | |
| 1.65.7 | 0 / 11 | |
| 1.65.3 | 0 / 11 | |
| 1.64.69 | 0 / 11 | |
| 1.64.68 | 0 / 11 | |
| 1.64.67 | 0 / 11 | |
| 1.64.65 | 0 / 11 | |
| 1.64.54 | 0 / 11 | |
| 1.64.40 | 0 / 11 | |
| 1.64.37 | 0 / 11 | |
| 1.64.32 | 0 / 11 | |
| 1.64.29 | 0 / 11 | |
| 1.64.26 | 0 / 11 | |
| 1.64.24 | 0 / 11 | |
| 1.64.20 | 0 / 11 | |
| 1.64.19 | 0 / 11 | |
| 1.64.14 | 0 / 11 | |
| 1.64.11 | 0 / 11 | |
| 1.64.9 | 0 / 11 | |
| 1.64.8 | 0 / 11 | |
| 1.64.7 | 0 / 11 |
v1.85.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.