@aman_asmuei/aman-agent
Your AI companion, running locally — powered by the aman ecosystem
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are same-org @aman_asmuei/* packages; consistent with ecosystem modularization, not supply-chain risk. | ai | |
| phantom-deps | phantom-dep:@aman_asmuei/aman-core | AI (phantom-deps): Same-org dep declared as transitive/re-export; phantom detection is a false positive for this package's architecture. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.26.0 | 13 / 5 | |
| 0.25.0 | 13 / 5 | |
| 0.23.0 | 13 / 5 | |
| 0.16.2 | 9 / 5 | |
| 0.8.0 | 9 / 5 | |
| 0.7.7 | 9 / 5 | |
| 0.7.6 | 9 / 5 | |
| 0.7.5 | 9 / 5 | |
| 0.7.4 | 9 / 5 | |
| 0.7.3 | 9 / 5 | |
| 0.7.2 | 9 / 5 | |
| 0.7.1 | 9 / 5 | |
| 0.7.0 | 9 / 5 | |
| 0.6.8 | 9 / 5 | |
| 0.6.7 | 9 / 5 | |
| 0.6.6 | 9 / 5 | |
| 0.6.5 | 9 / 5 | |
| 0.6.4 | 9 / 5 | |
| 0.6.3 | 9 / 5 | |
| 0.6.2 | 9 / 5 | |
| 0.6.1 | 9 / 5 | |
| 0.6.0 | 9 / 5 | |
| 0.5.1 | 6 / 4 | |
| 0.5.0 | 6 / 4 | |
| 0.4.0 | 6 / 4 | |
| 0.3.1 | 6 / 4 | |
| 0.3.0 | 6 / 4 | |
| 0.2.4 | 6 / 4 | |
| 0.2.3 | 6 / 4 | |
| 0.2.2 | 6 / 4 | |
| 0.2.1 | 6 / 4 | |
| 0.2.0 | 6 / 4 | |
| 0.1.0 | 5 / 4 |
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
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.1
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.