← Home

@mingto/microsoft-tts

借助“微软认知服务语音合成API”实现浏览器端“文本转语音

6
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

minto_marketing

Keywords

TTS文本转语音微软认知服务

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@mingto/tools AI (phantom-deps): Same-org scoped dep; likely used transitively or re-exported, stable false positive for this package. ai
phantom-deps phantom-dep:@mingto/text-stream-slicer AI (phantom-deps): Same-org scoped dep; likely used transitively or re-exported, stable false positive for this package. ai
provenance no-provenance AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.7 2 / 0
1.0.6 2 / 0
1.0.5 2 / 0
1.0.3 2 / 0
1.0.2 2 / 0
1.0.1 3 / 0

v1.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.