vscode-textmate
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate Microsoft org account consolidation; microsoft1es is the canonical Microsoft npm publisher. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Microsoft org accounts; consistent with org-level consolidation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are individual MS employees replaced by org accounts; expected in org consolidation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy followed by Microsoft org account publish; consistent with delayed org migration, not takeover. | ai | |
| provenance | missing-githead | AI (provenance): Changed publish environment (org consolidation) explains missing gitHead; no malicious indicators present. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 9.3.2 | 0 / 10 | |
| 9.3.1 | 0 / 10 | |
| 9.3.0 | 0 / 10 | |
| 9.2.1 | 0 / 10 | |
| 7.0.1 | 0 / 7 |
v9.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.
This version was published by a different npm account than previous versions on 2026-01-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.
This version was published by a different npm account than previous versions on 2025-12-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.
This version was published by a different npm account than previous versions on 2025-10-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.