@microsoft/mgt-element
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Template engine expression evaluator; stable pattern in this package across versions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.6.1 | 4 / 0 | |
| 4.6.0 | 4 / 0 | |
| 4.5.0 | 4 / 0 | |
| 4.4.0 | 4 / 0 | |
| 4.3.0 | 4 / 0 | |
| 4.2.5 | 4 / 0 | |
| 4.2.4 | 4 / 0 | |
| 4.2.3 | 4 / 0 | |
| 4.2.2 | 4 / 0 |
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.