@magic-xpa/angular-material-core
This package is part of Magic xpa Web Application Framework. It is used to easily create modern business apps powered by Angular to provide a rich user experience and meet the increasingly complex enterprise business expectations for digital transformati
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 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 4.1202.0 | 1 / 0 | |
| 4.1201.1 | 1 / 0 | |
| 4.1201.0 | 1 / 0 | |
| 4.1200.0 | 1 / 0 | |
| 4.1101.2 | 1 / 0 | |
| 4.1101.1 | 1 / 0 | |
| 4.1101.0 | 1 / 0 | |
| 4.1100.0 | 1 / 0 | |
| 4.800.2 | 1 / 0 | |
| 4.800.1 | 1 / 0 | |
| 4.800.0 | 1 / 0 | |
| 4.702.0 | 1 / 0 | |
| 4.701.0 | 1 / 0 | |
| 4.700.0 | 1 / 0 | |
| 4.602.0 | 1 / 0 | |
| 4.601.1 | 1 / 0 | |
| 4.601.0 | 1 / 0 | |
| 4.600.0 | 1 / 0 | |
| 4.6.0 | 1 / 0 | |
| 4.5.1 | 1 / 0 | |
| 4.5.0 | 1 / 0 |
v4.1101.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1101.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1101.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.800.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.800.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.800.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.702.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.701.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.700.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.602.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.601.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.601.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.600.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.