@alwaysmeticulous/client
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): 265 versions in registry; package is actively maintained. Dormancy signal is a false positive here. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; missing gitHead is a minor metadata gap, not a supply chain risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal SDK helper package; sparse README and no keywords are expected for monorepo utility packages. | ai |
Versions (showing 100 of 223)
| Version | Deps | Published |
|---|---|---|
| 2.239.3 | 5 / 0 | |
| 2.239.2 | 5 / 0 | |
| 2.239.1 | 5 / 0 | |
| 2.238.0 | 5 / 0 | |
| 2.237.1 | 5 / 0 | |
| 2.236.2 | 5 / 0 | |
| 2.236.0 | 5 / 0 | |
| 2.235.2 | 5 / 0 | |
| 2.235.1 | 5 / 0 | |
| 2.233.0 | 5 / 0 | |
| 2.232.0 | 5 / 0 | |
| 2.231.0 | 5 / 0 | |
| 2.230.0 | 5 / 0 | |
| 2.229.3 | 5 / 0 | |
| 2.229.2 | 5 / 0 | |
| 2.229.1 | 5 / 0 | |
| 2.229.0 | 5 / 0 | |
| 2.228.0 | 6 / 0 | |
| 2.227.1 | 5 / 0 | |
| 2.226.0 | 5 / 0 | |
| 2.225.0 | 5 / 0 | |
| 2.224.0 | 5 / 0 | |
| 2.223.0 | 5 / 0 | |
| 2.221.2 | 5 / 0 | |
| 2.221.0 | 5 / 0 | |
| 2.219.1 | 5 / 0 | |
| 2.219.0 | 5 / 0 | |
| 2.218.3 | 5 / 0 | |
| 2.218.2 | 5 / 0 | |
| 2.218.1 | 5 / 0 | |
| 2.218.0 | 5 / 0 | |
| 2.217.0 | 5 / 0 | |
| 2.216.2 | 5 / 0 | |
| 2.216.1 | 5 / 0 | |
| 2.216.0 | 5 / 0 | |
| 2.215.1 | 5 / 0 | |
| 2.215.0 | 5 / 0 | |
| 2.214.1 | 5 / 0 | |
| 2.214.0 | 5 / 0 | |
| 2.213.0 | 5 / 0 | |
| 2.212.0 | 5 / 0 | |
| 2.211.0 | 5 / 0 | |
| 2.210.0 | 5 / 0 | |
| 2.208.0 | 5 / 0 | |
| 2.206.5 | 5 / 0 | |
| 2.206.4 | 5 / 0 | |
| 2.206.3 | 5 / 0 | |
| 2.206.2 | 5 / 0 | |
| 2.206.1 | 5 / 0 | |
| 2.206.0 | 5 / 0 | |
| 2.205.0 | 5 / 0 | |
| 2.201.0 | 5 / 0 | |
| 2.200.0 | 5 / 0 | |
| 2.199.1 | 5 / 0 | |
| 2.199.0 | 5 / 0 | |
| 2.198.0 | 5 / 0 | |
| 2.196.0 | 5 / 0 | |
| 2.195.0 | 5 / 0 | |
| 2.194.1 | 5 / 0 | |
| 2.194.0 | 5 / 0 | |
| 2.192.0 | 5 / 0 | |
| 2.191.0 | 5 / 0 | |
| 2.190.0 | 5 / 0 | |
| 2.189.0 | 5 / 0 | |
| 2.188.0 | 5 / 0 | |
| 2.186.0 | 5 / 0 | |
| 2.185.1 | 5 / 0 | |
| 2.185.0 | 5 / 0 | |
| 2.184.0 | 5 / 0 | |
| 2.183.0 | 5 / 0 | |
| 2.181.1 | 5 / 0 | |
| 2.181.0 | 5 / 0 | |
| 2.180.0 | 5 / 0 | |
| 2.178.0 | 5 / 0 | |
| 2.177.0 | 5 / 0 | |
| 2.176.0 | 5 / 0 | |
| 2.175.0 | 5 / 0 | |
| 2.174.0 | 5 / 0 | |
| 2.173.0 | 5 / 0 | |
| 2.172.0 | 5 / 0 | |
| 2.171.0 | 5 / 0 | |
| 2.170.0 | 5 / 0 | |
| 2.169.0 | 5 / 0 | |
| 2.168.0 | 5 / 0 | |
| 2.167.0 | 5 / 0 | |
| 2.166.0 | 5 / 0 | |
| 2.165.0 | 5 / 0 | |
| 2.164.0 | 5 / 0 | |
| 2.163.0 | 5 / 0 | |
| 2.162.0 | 5 / 0 | |
| 2.161.0 | 5 / 0 | |
| 2.160.0 | 5 / 0 | |
| 2.159.0 | 5 / 0 | |
| 2.158.1 | 5 / 0 | |
| 2.157.0 | 5 / 0 | |
| 2.156.0 | 5 / 0 | |
| 2.155.0 | 5 / 0 | |
| 2.154.1 | 5 / 0 | |
| 2.154.0 | 5 / 0 | |
| 2.153.0 | 5 / 0 |
v2.218.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.218.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.218.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.218.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.217.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.216.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.216.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.216.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.215.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.215.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.214.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.214.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.213.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.212.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.211.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.210.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.208.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.206.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.206.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.206.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.206.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.206.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.206.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.205.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.201.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.200.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.199.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.199.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.198.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.196.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.195.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.194.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.194.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.192.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.191.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.190.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.189.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.188.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.186.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.185.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.185.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.184.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.183.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.181.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.181.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.180.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.178.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.177.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.176.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.175.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.174.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.173.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.172.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.171.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.170.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.169.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.168.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.167.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.166.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.165.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.164.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.163.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.162.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.161.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.160.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.159.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.158.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.157.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.156.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.155.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.154.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.154.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.153.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.