← Home

@agentuity/server

npm Repository Homepage
100
Versions
—
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

p0tofpiehuijirojhaynie

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established Agentuity org package; lack of Sigstore attestation is a process gap, not a security risk for this publisher. ai
provenance missing-githead AI (provenance): Agentuity monorepo; publisher has 1549 approved packages; missing gitHead is a CI process change, not a supply-chain indicator. ai
publish-pattern new-deps-added AI (publish-pattern): New dep is @agentuity/[email protected] — same org/version family, not a suspicious third-party package. ai
provenance publisher-changed AI (provenance): p0tofpie is a high-volume trusted publisher (1041 approved); transition appears to be an org-internal maintainer change. ai
semgrep semgrep:etc-passwd-access AI (semgrep): Fires on a JSDoc comment string showing invalid input examples, not actual /etc/passwd access. ai
bogus-package bogus-package AI (bogus-package): Internal SDK component; sparse metadata is consistent across all 254 versions of this package. ai
typosquat typosquat.levenshtein:semver AI (typosquat): Scoped @agentuity package; Levenshtein match to 'semver' is a false positive with no brand impersonation intent. ai

Versions (showing 100 of 211)

Version Deps Published
3.0.5 3 / 5
3.0.4 3 / 5
3.0.3 3 / 5
3.0.2 3 / 5
3.0.1 3 / 5
3.0.0 3 / 5
2.0.26 3 / 5
2.0.25 3 / 5
2.0.24 3 / 5
2.0.23 3 / 5
2.0.22 3 / 5
2.0.21 3 / 5
2.0.20 3 / 5
2.0.19 3 / 5
2.0.18 3 / 5
2.0.17 3 / 5
2.0.16 3 / 5
2.0.15 3 / 5
2.0.14 3 / 5
2.0.13 3 / 5
2.0.12 3 / 5
2.0.11 3 / 5
2.0.10 3 / 5
2.0.9 3 / 5
2.0.8 3 / 5
2.0.7 3 / 5
2.0.6 3 / 5
2.0.5 3 / 5
2.0.4 3 / 5
2.0.3 3 / 5
2.0.2 3 / 5
2.0.1 3 / 5
2.0.0 3 / 5
1.0.64 3 / 5
1.0.63 3 / 5
1.0.62 3 / 5
1.0.61 3 / 5
1.0.60 3 / 5
1.0.59 3 / 5
1.0.58 3 / 5
1.0.57 3 / 5
1.0.56 3 / 5
1.0.55 3 / 5
1.0.54 3 / 5
1.0.53 3 / 5
1.0.52 3 / 5
1.0.51 3 / 5
1.0.50 3 / 5
1.0.49 3 / 5
1.0.48 3 / 5
1.0.47 3 / 5
1.0.46 3 / 5
1.0.45 3 / 5
1.0.44 3 / 5
1.0.43 3 / 5
1.0.42 3 / 5
1.0.41 3 / 5
1.0.40 3 / 5
1.0.39 3 / 5
1.0.38 3 / 5
1.0.37 3 / 5
1.0.36 3 / 5
1.0.35 3 / 5
1.0.34 3 / 5
1.0.33 3 / 5
1.0.32 3 / 5
1.0.31 3 / 5
1.0.30 3 / 5
1.0.29 3 / 5
1.0.28 3 / 5
1.0.27 3 / 5
1.0.26 3 / 5
1.0.25 3 / 5
1.0.24 3 / 5
1.0.23 3 / 5
1.0.22 3 / 5
1.0.21 3 / 5
1.0.20 3 / 5
1.0.19 3 / 5
1.0.18 3 / 5
1.0.17 3 / 5
1.0.16 3 / 5
1.0.15 3 / 5
1.0.14 3 / 5
1.0.13 3 / 5
1.0.12 3 / 5
1.0.11 3 / 5
1.0.10 3 / 5
1.0.9 3 / 5
1.0.8 3 / 5
1.0.7 3 / 5
1.0.6 3 / 5
1.0.5 3 / 5
1.0.4 3 / 5
1.0.3 3 / 5
1.0.2 3 / 5
1.0.1 3 / 5
1.0.0 3 / 5
0.1.45 3 / 5
0.1.44 3 / 5
Showing 100 of 211 Next page →

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

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jhaynie → huijiro (on 2026-05-25, known maintainer) provenance

This version was published by a different npm account (huijiro) than the most recent previously approved version (jhaynie) on 2026-05-25, but huijiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.0.26

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: huijiro.

v2.0.25

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: huijiro.

LOW No provenance attestation provenance

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

v2.0.24

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: huijiro.

LOW No provenance attestation provenance

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

v2.0.23

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: huijiro.

LOW No provenance attestation provenance

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

v2.0.22

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: p0tofpie.

LOW No provenance attestation provenance

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

INFO Publisher changed: huijiro → p0tofpie (on 2026-05-27, known maintainer) provenance

This version was published by a different npm account (p0tofpie) than the most recent previously approved version (huijiro) on 2026-05-27, but p0tofpie is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.0.21

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.20

1 finding
LOW No provenance attestation provenance

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

v2.0.19

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.18

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.17

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.16

1 finding
LOW No provenance attestation provenance

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

v2.0.15

1 finding
LOW No provenance attestation provenance

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

v2.0.14

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.13

1 finding
LOW No provenance attestation provenance

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

v2.0.12

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.11

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.10

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.9

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.8

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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.

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.0.64

1 finding
LOW No provenance attestation provenance

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

v1.0.63

1 finding
LOW No provenance attestation provenance

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

v1.0.62

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

2 findings
HIGH Publisher changed: jhaynie → p0tofpie (on 2026-03-26) provenance

This version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.60

1 finding
LOW No provenance attestation provenance

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

v1.0.59

1 finding
LOW No provenance attestation provenance

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

v1.0.58

1 finding
LOW No provenance attestation provenance

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

v1.0.57

1 finding
LOW No provenance attestation provenance

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

v1.0.56

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

1 finding
LOW No provenance attestation provenance

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

v1.0.54

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

2 findings
HIGH Publisher changed: jhaynie → p0tofpie (on 2026-03-19) provenance

This version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.52

1 finding
LOW No provenance attestation provenance

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

v1.0.51

1 finding
LOW No provenance attestation provenance

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

v1.0.50

1 finding
LOW No provenance attestation provenance

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

v1.0.49

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

1 finding
LOW No provenance attestation provenance

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

v1.0.46

1 finding
LOW No provenance attestation provenance

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

v1.0.45

1 finding
LOW No provenance attestation provenance

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

v1.0.44

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

1 finding
LOW No provenance attestation provenance

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

v1.0.42

1 finding
LOW No provenance attestation provenance

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

v1.0.41

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

1 finding
LOW No provenance attestation provenance

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

v1.0.39

1 finding
LOW No provenance attestation provenance

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

v1.0.38

1 finding
LOW No provenance attestation provenance

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

v1.0.37

1 finding
LOW No provenance attestation provenance

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

v1.0.36

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

1 finding
LOW No provenance attestation provenance

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

v1.0.34

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

1 finding
LOW No provenance attestation provenance

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

v1.0.32

1 finding
LOW No provenance attestation provenance

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

v1.0.31

1 finding
LOW No provenance attestation provenance

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

v1.0.30

1 finding
LOW No provenance attestation provenance

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

v1.0.29

1 finding
LOW No provenance attestation provenance

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

v1.0.28

1 finding
LOW No provenance attestation provenance

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

v1.0.27

1 finding
LOW No provenance attestation provenance

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

v1.0.26

1 finding
LOW No provenance attestation provenance

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

v1.0.25

1 finding
LOW No provenance attestation provenance

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

v1.0.24

1 finding
LOW No provenance attestation provenance

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

v1.0.23

3 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

HIGH etc-passwd-access: src/api/sandbox/snapshot-build.ts:11 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 9 | * "https://github.com/user/repo", "git+https://github.com/user/repo.git", 10 | * "github:user/repo", "file:../local-pkg" > 11 | * Invalid examples: "foo bar", "pkg;rm -rf", "pkg|cat /etc/passwd", "$(evil)" 12 | */ 13 | export const NPM_PACKAGE_NAME_PATTERN = /^[^\s;`|$]+$/;

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

1 finding
LOW No provenance attestation provenance

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

v1.0.21

3 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

HIGH etc-passwd-access: src/api/sandbox/snapshot-build.ts:11 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 9 | * "https://github.com/user/repo", "git+https://github.com/user/repo.git", 10 | * "github:user/repo", "file:../local-pkg" > 11 | * Invalid examples: "foo bar", "pkg;rm -rf", "pkg|cat /etc/passwd", "$(evil)" 12 | */ 13 | export const NPM_PACKAGE_NAME_PATTERN = /^[^\s;`|$]+$/;

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

3 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

HIGH etc-passwd-access: src/api/sandbox/snapshot-build.ts:11 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 9 | * "https://github.com/user/repo", "git+https://github.com/user/repo.git", 10 | * "github:user/repo", "file:../local-pkg" > 11 | * Invalid examples: "foo bar", "pkg;rm -rf", "pkg|cat /etc/passwd", "$(evil)" 12 | */ 13 | export const NPM_PACKAGE_NAME_PATTERN = /^[^\s;`|$]+$/;

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

1 finding
LOW No provenance attestation provenance

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

v1.0.18

3 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

HIGH etc-passwd-access: src/api/sandbox/snapshot-build.ts:11 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 9 | * "https://github.com/user/repo", "git+https://github.com/user/repo.git", 10 | * "github:user/repo", "file:../local-pkg" > 11 | * Invalid examples: "foo bar", "pkg;rm -rf", "pkg|cat /etc/passwd", "$(evil)" 12 | */ 13 | export const NPM_PACKAGE_NAME_PATTERN = /^[^\s;`|$]+$/;

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

1 finding
LOW No provenance attestation provenance

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

v1.0.16

3 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

HIGH etc-passwd-access: src/api/sandbox/snapshot-build.ts:11 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 9 | * "https://github.com/user/repo", "git+https://github.com/user/repo.git", 10 | * "github:user/repo", "file:../local-pkg" > 11 | * Invalid examples: "foo bar", "pkg;rm -rf", "pkg|cat /etc/passwd", "$(evil)" 12 | */ 13 | export const NPM_PACKAGE_NAME_PATTERN = /^[^\s;`|$]+$/;

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

1 finding
LOW No provenance attestation provenance

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

v1.0.14

1 finding
LOW No provenance attestation provenance

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

v1.0.13

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

1 finding
LOW No provenance attestation provenance

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

v1.0.11

1 finding
LOW No provenance attestation provenance

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

v1.0.10

1 finding
LOW No provenance attestation provenance

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

v1.0.9

1 finding
LOW No provenance attestation provenance

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

v1.0.8

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

2 findings
HIGH Publisher changed: jhaynie → p0tofpie (on 2026-02-10) provenance

This version was published by a different npm account than previous versions on 2026-02-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.1.45

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.

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

1 finding
LOW No provenance attestation provenance

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