@sandagent/daemon
SandAgent Daemon - Unified API gateway for sandbox services (file, git, volumes)
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): DAX_HEX is a bundled upstream dep (pi-coding-agent/daxnuts.js); consistent hex color/pixel data, not a payload. | ai | |
| source-diff | encoded-string-file:dist/nextjs.js | AI (source-diff): Same DAX_HEX from bundled upstream dep; stable false positive for this package. | ai | |
| source-diff | encoded-string-file:dist/bundle.mjs | AI (source-diff): Same DAX_HEX from bundled upstream dep; stable false positive for this package. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.9.28 | 0 / 5 | |
| 0.9.27 | 0 / 5 | |
| 0.9.26 | 0 / 5 | |
| 0.9.25 | 0 / 5 | |
| 0.9.24 | 0 / 5 | |
| 0.9.23 | 0 / 5 | |
| 0.9.22 | 0 / 5 | |
| 0.9.21 | 0 / 5 | |
| 0.9.20 | 0 / 5 | |
| 0.9.19 | 0 / 5 | |
| 0.9.18 | 0 / 5 | |
| 0.9.17 | 0 / 5 | |
| 0.9.16 | 0 / 5 | |
| 0.9.15 | 0 / 5 | |
| 0.9.14 | 0 / 5 | |
| 0.9.13 | 0 / 5 | |
| 0.9.12 | 0 / 5 | |
| 0.9.11 | 0 / 5 | |
| 0.9.10 | 0 / 5 | |
| 0.9.9 | 0 / 5 | |
| 0.9.8 | 0 / 5 | |
| 0.9.7 | 0 / 5 | |
| 0.9.6 | 0 / 5 | |
| 0.9.5 | 0 / 5 | |
| 0.9.4 | 0 / 5 | |
| 0.9.3 | 0 / 5 | |
| 0.9.2 | 0 / 5 | |
| 0.9.1 | 0 / 5 | |
| 0.9.0 | 0 / 5 | |
| 0.8.10 | 0 / 5 | |
| 0.8.9 | 0 / 5 | |
| 0.8.8 | 0 / 5 | |
| 0.8.7 | 0 / 5 | |
| 0.8.6 | 0 / 5 |
v0.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.