@agentuity/server
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 |
|---|---|---|---|---|
| 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 11 of 219)
| Version | Deps | Published |
|---|---|---|
| 0.0.53 | 2 / 4 | |
| 0.0.52 | 2 / 4 | |
| 0.0.51 | 2 / 4 | |
| 0.0.50 | 2 / 4 | |
| 0.0.49 | 2 / 2 | |
| 0.0.48 | 2 / 2 | |
| 0.0.47 | 2 / 2 | |
| 0.0.46 | 2 / 2 | |
| 0.0.45 | 2 / 2 | |
| 0.0.44 | 2 / 2 | |
| 0.0.43 | 2 / 2 |
v0.0.53
2 findingsPackage name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.52
2 findingsPackage name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
2 findingsPackage name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
2 findingsPackage name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.45
2 findingsPackage name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.43
2 findingsPackage name '@agentuity/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.