@agentuity/core
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval('require') used explicitly to avoid bundler static analysis — documented pattern, not malicious. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @agentuity/core is not a typosquat of cors; different namespace and purpose. | ai | |
| semgrep | semgrep:etc-passwd-access | AI (semgrep): /etc/passwd reference is inside a JSDoc comment illustrating invalid input examples, not executable code. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Requires a resolved package.json URL for version detection; not arbitrary module loading. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes workbench config passed by the platform; not obfuscated payload execution. | ai |
Versions (showing 100 of 206)
| Version | Deps | Published |
|---|---|---|
| 3.0.5 | 1 / 4 | |
| 3.0.4 | 1 / 4 | |
| 3.0.3 | 1 / 4 | |
| 3.0.2 | 1 / 4 | |
| 3.0.1 | 1 / 4 | |
| 3.0.0 | 1 / 4 | |
| 2.0.21 | 1 / 5 | |
| 2.0.20 | 1 / 5 | |
| 2.0.19 | 1 / 5 | |
| 2.0.18 | 1 / 5 | |
| 2.0.17 | 1 / 5 | |
| 2.0.16 | 1 / 5 | |
| 2.0.15 | 1 / 5 | |
| 2.0.14 | 1 / 5 | |
| 2.0.13 | 1 / 5 | |
| 2.0.12 | 1 / 5 | |
| 2.0.11 | 1 / 5 | |
| 2.0.10 | 1 / 5 | |
| 2.0.9 | 1 / 5 | |
| 2.0.8 | 1 / 5 | |
| 2.0.7 | 1 / 5 | |
| 2.0.6 | 1 / 5 | |
| 2.0.5 | 1 / 5 | |
| 2.0.4 | 1 / 5 | |
| 2.0.3 | 1 / 5 | |
| 2.0.2 | 1 / 5 | |
| 2.0.1 | 1 / 5 | |
| 2.0.0 | 1 / 5 | |
| 1.0.64 | 1 / 5 | |
| 1.0.63 | 1 / 5 | |
| 1.0.62 | 1 / 5 | |
| 1.0.61 | 1 / 5 | |
| 1.0.60 | 1 / 5 | |
| 1.0.59 | 1 / 5 | |
| 1.0.58 | 1 / 5 | |
| 1.0.57 | 1 / 5 | |
| 1.0.56 | 1 / 5 | |
| 1.0.55 | 1 / 5 | |
| 1.0.54 | 1 / 5 | |
| 1.0.53 | 1 / 5 | |
| 1.0.52 | 1 / 5 | |
| 1.0.51 | 1 / 5 | |
| 1.0.50 | 1 / 5 | |
| 1.0.49 | 1 / 5 | |
| 1.0.48 | 1 / 5 | |
| 1.0.47 | 1 / 5 | |
| 1.0.46 | 1 / 5 | |
| 1.0.45 | 1 / 5 | |
| 1.0.44 | 1 / 5 | |
| 1.0.43 | 1 / 5 | |
| 1.0.42 | 1 / 5 | |
| 1.0.41 | 1 / 5 | |
| 1.0.40 | 1 / 5 | |
| 1.0.39 | 1 / 5 | |
| 1.0.38 | 1 / 5 | |
| 1.0.37 | 1 / 5 | |
| 1.0.36 | 1 / 5 | |
| 1.0.35 | 1 / 5 | |
| 1.0.34 | 1 / 5 | |
| 1.0.33 | 1 / 5 | |
| 1.0.32 | 1 / 5 | |
| 1.0.31 | 1 / 5 | |
| 1.0.30 | 1 / 5 | |
| 1.0.29 | 1 / 5 | |
| 1.0.28 | 1 / 5 | |
| 1.0.27 | 1 / 5 | |
| 1.0.26 | 1 / 5 | |
| 1.0.25 | 1 / 5 | |
| 1.0.24 | 1 / 5 | |
| 1.0.23 | 1 / 5 | |
| 1.0.22 | 1 / 5 | |
| 1.0.21 | 1 / 5 | |
| 1.0.20 | 1 / 5 | |
| 1.0.19 | 1 / 5 | |
| 1.0.18 | 1 / 5 | |
| 1.0.17 | 1 / 5 | |
| 1.0.16 | 1 / 5 | |
| 1.0.15 | 1 / 5 | |
| 1.0.14 | 1 / 5 | |
| 1.0.13 | 1 / 5 | |
| 1.0.12 | 1 / 5 | |
| 1.0.11 | 1 / 5 | |
| 1.0.10 | 1 / 5 | |
| 1.0.9 | 1 / 5 | |
| 1.0.8 | 1 / 5 | |
| 1.0.7 | 1 / 5 | |
| 1.0.6 | 1 / 5 | |
| 1.0.5 | 1 / 5 | |
| 1.0.4 | 1 / 5 | |
| 1.0.3 | 1 / 5 | |
| 1.0.2 | 1 / 5 | |
| 1.0.1 | 1 / 5 | |
| 1.0.0 | 1 / 5 | |
| 0.1.45 | 1 / 5 | |
| 0.1.44 | 1 / 5 | |
| 0.1.43 | 1 / 5 | |
| 0.1.42 | 1 / 5 | |
| 0.1.41 | 1 / 5 | |
| 0.1.40 | 1 / 5 | |
| 0.1.39 | 1 / 5 |
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.21
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.64
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.63
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.62
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.61
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.60
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.59
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.58
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.57
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.56
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.54
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.52
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.51
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.42
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.40
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.39
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
3 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
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;`|$]+$/;
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.41
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
2 findingsPackage name '@agentuity/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.