@azure/ai-projects
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit dependency in Azure SDK ecosystem; stable across versions. | ai | |
| phantom-deps | phantom-dep:@azure/core-sse | AI (phantom-deps): Framework-scoped Azure package loaded by convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:@azure/core-util | AI (phantom-deps): Framework-scoped Azure package loaded by convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:@azure/core-tracing | AI (phantom-deps): Framework-scoped Azure package loaded by convention; stable pattern. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 14 / 27 | |
| 2.3.0 | 14 / 27 | |
| 2.2.0 | 14 / 27 | |
| 2.1.1 | 14 / 26 | |
| 2.1.0 | 14 / 26 | |
| 2.0.2 | 14 / 26 | |
| 2.0.1 | 14 / 26 | |
| 2.0.0 | 14 / 26 |
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.