← Home

@microsoft/agent-os-copilot-extension

Public Preview — AgentOS GitHub Copilot Extension: Build safe AI agents with natural language and 0% policy violations

13
Versions
MIT
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

microsoft1esmicrosoft-oss-releases

Keywords

githubcopilotextensionsafetyaiagentscode-reviewsecurityagent-oscompliancegdprhipaasoc2

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): child_process used in deploy.js helper, not in install scripts or runtime code paths that could be exploited. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): Raw IP 127.0.0.1 is localhost used in test setup; not a network exfiltration risk. ai
phantom-deps phantom-dep:path-to-regexp AI (phantom-deps): Transitive/indirect dependency used by express; stable false positive for this package. ai
phantom-deps phantom-dep:@octokit/webhooks AI (phantom-deps): Declared runtime dep used via config/type references; stable false positive for this package. ai

Versions (showing 13 of 13)

Version Deps Published
4.0.0 6 / 10
3.7.0 6 / 10
3.6.0 6 / 10
3.5.0 6 / 10
3.4.0 6 / 10
3.3.0 6 / 10
3.2.2 6 / 10
3.2.1 6 / 10
3.2.0 6 / 10
3.1.0 6 / 10
3.0.2 6 / 10
1.0.1 6 / 10
1.0.0 6 / 10

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.7.0

1 finding
LOW No provenance attestation provenance

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

v3.6.0

1 finding
LOW No provenance attestation provenance

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

v3.5.0

1 finding
LOW No provenance attestation provenance

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

v3.4.0

1 finding
LOW No provenance attestation provenance

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

v3.3.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.

v3.2.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.

v3.2.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.

v3.2.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.

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

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

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.