@sap-devx/app-studio-toolkit-types
The SAP Business Application Studio Toolkit VSCode Extension's API type signatures
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate SAP org workflow migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD migration is consistent with SAP org tooling changes, not account takeover. | ai | |
| dependencies | unvetted-dep:@sap/artifact-management-types | AI (dependencies): SAP-scoped types dependency consistent with this SAP types package; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@types/vscode | AI (phantom-deps): VSCode extension types package; framework-scoped, loaded by convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:@vscode-logging/types | AI (phantom-deps): Referenced in config files only; stable false positive for this types-only package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.11.2 | 4 / 0 | |
| 2.11.1 | 4 / 0 | |
| 2.11.0 | 4 / 0 | |
| 2.10.1 | 4 / 0 | |
| 2.10.0 | 4 / 0 | |
| 2.9.0 | 4 / 0 | |
| 2.8.0 | 4 / 0 | |
| 2.7.0 | 4 / 0 | |
| 2.6.0 | 4 / 0 | |
| 2.5.0 | 4 / 0 |
v2.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.