@agentuity/analytics
Browser analytics for Agentuity applications
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer; one-off environment change, not indicative of supply chain compromise. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 3.1.14 | 0 / 3 | |
| 3.1.13 | 0 / 3 | |
| 3.1.12 | 0 / 3 | |
| 3.1.11 | 0 / 3 | |
| 3.1.10 | 0 / 3 | |
| 3.1.9 | 0 / 3 | |
| 3.1.8 | 0 / 3 | |
| 3.1.7 | 0 / 3 | |
| 3.1.6 | 0 / 3 | |
| 3.1.5 | 0 / 3 | |
| 3.1.4 | 0 / 3 | |
| 3.1.3 | 0 / 3 | |
| 3.1.2 | 0 / 3 | |
| 3.1.1 | 0 / 3 | |
| 3.1.0 | 0 / 3 | |
| 3.0.12 | 0 / 3 | |
| 3.0.11 | 0 / 3 | |
| 3.0.10 | 0 / 3 | |
| 3.0.9 | 0 / 3 | |
| 3.0.8 | 0 / 3 | |
| 3.0.7 | 0 / 3 | |
| 3.0.6 | 0 / 3 | |
| 3.0.5 | 0 / 3 | |
| 3.0.4 | 0 / 3 | |
| 3.0.3 | 0 / 3 | |
| 3.0.2 | 0 / 3 | |
| 3.0.1 | 0 / 3 | |
| 3.0.0 | 0 / 3 |
v3.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
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 (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 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-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 findingsPackage 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
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 (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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
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-06-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.