@sassoftware/sas-score-mcp-serverjs Apache-2.0 27 versions

@sassoftware/sas-score-mcp-serverjs

npm Repository Homepage

A mcp server for SAS Viya

27

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 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

coalmanjefurbeedevakumaraswamyckedwardsrbtleveybrmorrbjtomlinjolynamtlsmcmtlstgryanauldsaskenjacksonmtlhmomartin-coutts-sasromacftimothy.crider-sasdaarthewsken_sasmtlcmcmtlnshtom-mceachan_sasinst

Keywords

SAS Viyamcp-serverjsAgentic AIViya actionsrestafrestafeditrestaflibmodel context protocol

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): SAS org package; provenance absence is common and not a risk indicator here.	ai	2026/05/22
phantom-deps	phantom-dep:uuid	AI (phantom-deps): Declared dep, likely used indirectly or in config; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:helmet	AI (phantom-deps): Declared dep, likely used indirectly or in config; stable false positive for this package.	ai	2026/05/15
semgrep	semgrep:child-process-import	AI (semgrep): Used only to auto-open browser via platform-specific command; benign pattern stable for this package.	ai	2026/05/15
phantom-deps	phantom-dep:express-rate-limit	AI (phantom-deps): Declared dep, likely used indirectly or in config; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:express-list-endpoints	AI (phantom-deps): Declared dep, likely used indirectly or in config; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:cross-env	AI (phantom-deps): Used in npm scripts; phantom-dep heuristic doesn't apply to script-only deps.	ai	2026/05/15

Versions (showing 27 of 27)

Version	Deps	Published
1.0.0	20 / 8	2026-04-22
0.4.1	22 / 9	2026-03-31
0.4.0	22 / 9	2026-03-31
0.3.19	22 / 9	2026-02-26
0.3.18	22 / 9	2026-02-26
0.3.17	22 / 9	2026-02-25
0.3.16	22 / 9	2026-02-25
0.3.15	22 / 9	2026-02-24
0.3.14	22 / 9	2026-02-19
0.3.12	22 / 9	2026-02-18
0.3.11	22 / 9	2026-02-16
0.3.9	22 / 9	2026-02-14
0.3.8	22 / 9	2026-02-13
0.3.7	22 / 9	2026-02-10
0.3.6	22 / 9	2026-02-10
0.3.5	22 / 9	2026-02-09
0.3.4	22 / 9	2026-02-07
0.3.3	22 / 9	2026-02-06
0.3.2	22 / 9	2026-02-04
0.3.1	22 / 9	2026-02-04
0.3.0	22 / 9	2026-01-31
0.2.2	22 / 9	2026-01-30
0.2.1	22 / 9	2026-01-30
0.1.1	19 / 9	2026-01-15
0.1.0	19 / 9	2025-12-29
0.0.3	21 / 9	2025-12-24
0.0.2	21 / 9	2025-12-24

v1.0.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.

v0.4.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.19

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.18

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.17

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.16

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.15

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.14

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.12

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.11

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.9

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.8

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.7

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.6

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.5

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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.

v0.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.

v0.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.