@agentuity/sandbox
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@agentuity/api | AI (dependencies): First-party @agentuity sibling pinned to matched monorepo version. | ai | |
| provenance | missing-githead | AI (provenance): Metadata gap only; no behavior change, diff vs prior approved version is empty. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore attestation alone is not a malicious signal. | ai | |
| provenance | publisher-changed | AI (provenance): p0tofpie is an established publisher (2033 approved) within the Agentuity org; transition appears legitimate. | ai | |
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Match is a JSDoc comment listing invalid/rejected inputs in a package-spec injection validator; not fs access to /etc/passwd. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is consistent with an internal scoped package; not indicative of spam or malware for this org. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 3.1.7 | 6 / 3 | |
| 3.1.5 | 6 / 3 | |
| 3.1.3 | 6 / 3 | |
| 3.0.12 | 1 / 3 | |
| 3.0.11 | 1 / 3 | |
| 3.0.10 | 1 / 3 | |
| 3.0.9 | 1 / 3 | |
| 3.0.8 | 1 / 3 | |
| 3.0.7 | 1 / 3 | |
| 3.0.6 | 1 / 3 | |
| 3.0.5 | 1 / 3 | |
| 3.0.4 | 1 / 3 | |
| 3.0.3 | 1 / 3 | |
| 3.0.2 | 1 / 3 | |
| 3.0.1 | 1 / 3 | |
| 3.0.0 | 1 / 3 | |
| 2.0.30 | 1 / 1 | |
| 2.0.29 | 1 / 1 | |
| 2.0.28 | 1 / 1 | |
| 2.0.27 | 1 / 1 | |
| 2.0.26 | 1 / 1 | |
| 2.0.25 | 1 / 1 | |
| 2.0.24 | 1 / 1 | |
| 2.0.23 | 1 / 1 | |
| 2.0.22 | 1 / 1 | |
| 2.0.21 | 1 / 1 | |
| 2.0.20 | 1 / 1 | |
| 2.0.19 | 1 / 1 | |
| 2.0.18 | 1 / 1 | |
| 2.0.17 | 1 / 1 | |
| 2.0.16 | 1 / 1 | |
| 2.0.15 | 1 / 1 | |
| 2.0.14 | 1 / 1 | |
| 2.0.13 | 1 / 1 | |
| 2.0.12 | 1 / 1 | |
| 2.0.11 | 1 / 1 | |
| 2.0.10 | 1 / 1 | |
| 2.0.9 | 1 / 1 | |
| 2.0.8 | 1 / 1 | |
| 2.0.7 | 1 / 1 | |
| 2.0.6 | 1 / 1 | |
| 2.0.5 | 1 / 1 | |
| 2.0.4 | 1 / 1 | |
| 2.0.3 | 1 / 1 | |
| 2.0.2 | 1 / 1 | |
| 2.0.1 | 1 / 1 | |
| 2.0.0 | 1 / 1 | |
| 1.0.64 | 1 / 1 | |
| 1.0.63 | 1 / 1 | |
| 1.0.62 | 1 / 1 | |
| 1.0.61 | 1 / 1 | |
| 1.0.60 | 1 / 1 | |
| 1.0.59 | 1 / 1 | |
| 1.0.58 | 1 / 1 | |
| 1.0.57 | 1 / 1 | |
| 1.0.56 | 1 / 1 | |
| 1.0.55 | 1 / 1 | |
| 1.0.54 | 1 / 1 |
v3.1.7
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: huijiro.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux (matched inside a comment — likely documentation, not executed code) 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. 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-07-03, 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.
v3.1.5
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: huijiro.
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. 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-06-29, 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.30
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: p0tofpie.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (p0tofpie) than the most recent previously approved version (jhaynie) on 2026-06-25, 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.