@agentuity/vector
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish environment change within same org; no other malware indicators present. | ai | |
| npm-metadata | no-description | AI (npm-metadata): @agentuity/vector is an internal org package; sparse metadata is consistent across its version history. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @agentuity/server at the same version (2.0.22) — same-org sibling, not a third-party risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is a consistent trait of this org's packages; not indicative of malicious intent. | ai | |
| provenance | no-provenance | AI (provenance): Org-wide pattern; no provenance across all @agentuity packages, not a per-version anomaly. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 3.1.14 | 4 / 3 | |
| 3.1.13 | 4 / 3 | |
| 3.1.12 | 4 / 3 | |
| 3.1.11 | 4 / 3 | |
| 3.1.10 | 4 / 3 | |
| 3.1.9 | 4 / 3 | |
| 3.1.8 | 4 / 3 | |
| 3.1.7 | 4 / 3 | |
| 3.1.6 | 4 / 3 | |
| 3.1.5 | 4 / 3 | |
| 3.1.4 | 4 / 3 | |
| 3.1.3 | 4 / 3 | |
| 3.1.2 | 4 / 3 | |
| 3.1.1 | 4 / 3 | |
| 3.1.0 | 4 / 3 | |
| 3.0.12 | 3 / 3 | |
| 3.0.11 | 3 / 3 | |
| 3.0.10 | 3 / 3 | |
| 3.0.9 | 3 / 3 | |
| 3.0.8 | 3 / 3 | |
| 3.0.7 | 3 / 3 | |
| 3.0.6 | 3 / 3 | |
| 3.0.5 | 3 / 3 | |
| 3.0.4 | 3 / 3 | |
| 3.0.3 | 3 / 3 | |
| 3.0.2 | 3 / 3 | |
| 3.0.1 | 3 / 3 | |
| 3.0.0 | 3 / 3 | |
| 2.0.30 | 3 / 4 | |
| 2.0.29 | 3 / 4 | |
| 2.0.28 | 3 / 4 | |
| 2.0.27 | 3 / 4 | |
| 2.0.26 | 3 / 4 | |
| 2.0.25 | 3 / 4 | |
| 2.0.24 | 3 / 4 | |
| 2.0.23 | 3 / 4 | |
| 2.0.22 | 3 / 4 | |
| 2.0.21 | 3 / 4 | |
| 2.0.20 | 3 / 4 | |
| 2.0.19 | 3 / 4 | |
| 2.0.18 | 3 / 4 | |
| 2.0.17 | 3 / 4 | |
| 2.0.16 | 3 / 4 | |
| 2.0.15 | 3 / 4 | |
| 2.0.14 | 3 / 4 | |
| 2.0.13 | 3 / 4 | |
| 2.0.12 | 3 / 4 | |
| 2.0.11 | 3 / 4 | |
| 2.0.10 | 3 / 4 | |
| 2.0.9 | 3 / 4 | |
| 2.0.8 | 3 / 4 |
v3.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-20, but jhaynie 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.9
2 findings[Accepted risk] 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-08, 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.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-06, but jhaynie 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.7
2 findings[Accepted risk] 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.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-02, but jhaynie 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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.30
2 findings[Accepted risk] 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 (huijiro) 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.