@azure-tools/typespec-autorest
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Both azure-sdk and microsoft1es are Microsoft org accounts; transition is consistent with internal npm account consolidation. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.70.1 | 1 / 17 | |
| 0.70.0 | 1 / 17 | |
| 0.69.1 | 0 / 17 | |
| 0.69.0 | 0 / 17 | |
| 0.68.0 | 0 / 17 | |
| 0.67.0 | 0 / 18 | |
| 0.66.2 | 0 / 18 | |
| 0.66.1 | 0 / 18 | |
| 0.66.0 | 0 / 18 | |
| 0.65.0 | 0 / 18 | |
| 0.64.1 | 0 / 18 | |
| 0.64.0 | 0 / 18 | |
| 0.63.1 | 0 / 18 | |
| 0.63.0 | 0 / 18 | |
| 0.62.0 | 0 / 18 | |
| 0.61.1 | 0 / 18 | |
| 0.61.0 | 0 / 18 | |
| 0.60.0 | 0 / 18 | |
| 0.59.1 | 0 / 18 | |
| 0.59.0 | 0 / 18 | |
| 0.58.1 | 0 / 18 | |
| 0.58.0 | 0 / 18 | |
| 0.57.1 | 0 / 19 | |
| 0.57.0 | 0 / 19 | |
| 0.56.0 | 0 / 19 | |
| 0.55.0 | 0 / 19 | |
| 0.54.0 | 0 / 19 | |
| 0.53.0 | 0 / 19 | |
| 0.52.0 | 0 / 19 | |
| 0.51.0 | 0 / 19 | |
| 0.50.0 | 0 / 19 | |
| 0.49.0 | 0 / 19 | |
| 0.48.0 | 0 / 19 | |
| 0.47.0 | 0 / 19 | |
| 0.46.0 | 0 / 19 | |
| 0.45.0 | 0 / 19 | |
| 0.44.1 | 0 / 19 | |
| 0.44.0 | 0 / 19 | |
| 0.43.0 | 0 / 19 | |
| 0.42.1 | 0 / 18 | |
| 0.42.0 | 0 / 18 |
v0.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.