← Home

@transcend-io/mcp-server-dsr

npm Repository Homepage

Transcend MCP Server — DSR Automation tools.

11
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

cami-transcendmichaelfarrell76bencmbrookdmattiaelidawson.turechekaldobarr

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@transcend-io/privacy-types AI (dependencies): Sibling workspace package from the same Transcend monorepo; not an external third-party risk. ai
dependencies unvetted-dep:@transcend-io/mcp-server-core AI (dependencies): Sibling workspace package from the same Transcend monorepo; not an external third-party risk. ai
phantom-deps phantom-dep:zod AI (phantom-deps): zod is a declared dependency used transitively/re-exported; phantom-dep is a false positive for this package. ai
phantom-deps phantom-dep:@modelcontextprotocol/sdk AI (phantom-deps): SDK is a declared dependency used transitively via mcp-server-base; phantom-dep is a false positive for this package. ai

Versions (showing 11 of 11)

Version Deps Published
0.3.8 4 / 6
0.3.7 4 / 6
0.3.6 4 / 6
0.3.5 4 / 6
0.3.4 4 / 6
0.3.3 4 / 6
0.3.2 4 / 6
0.3.1 4 / 6
0.3.0 4 / 6
0.2.0 4 / 6
0.1.0 4 / 6

v0.3.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.0

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.