@stackone/agent-harness
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared dependency; used via config and transitive imports in agent framework. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Declared dependency; used via config files in agent framework. | ai | |
| phantom-deps | phantom-dep:langsmith | AI (phantom-deps): Declared dependency; used via transitive imports in agent framework. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.12.1 | 3 / 10 | |
| 0.12.0 | 3 / 10 | |
| 0.10.0 | 4 / 10 | |
| 0.9.2 | 4 / 7 | |
| 0.9.1 | 4 / 7 | |
| 0.9.0 | 4 / 7 | |
| 0.8.1 | 4 / 7 | |
| 0.7.3 | 4 / 7 | |
| 0.7.2 | 4 / 7 | |
| 0.7.1 | 4 / 7 | |
| 0.7.0 | 4 / 7 | |
| 0.6.0 | 4 / 7 | |
| 0.5.0 | 4 / 7 | |
| 0.4.6 | 4 / 7 | |
| 0.4.5 | 4 / 7 | |
| 0.4.4 | 4 / 7 | |
| 0.4.3 | 4 / 7 | |
| 0.4.2 | 4 / 7 | |
| 0.4.1 | 4 / 7 | |
| 0.4.0 | 4 / 7 |
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.