@alwaysmeticulous/sentry
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): alwaysmeticulous/meticulous-sdk publishes via GitHub Actions with SLSA provenance; this is the expected CI/CD publisher pattern for this org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established SDK helper package; sparse README/no keywords is a style issue, not a security signal. | ai |
Versions (showing 100 of 158)
| Version | Deps | Published |
|---|---|---|
| 2.283.2 | 3 / 1 | |
| 2.283.1 | 3 / 1 | |
| 2.280.0 | 3 / 1 | |
| 2.277.0 | 3 / 1 | |
| 2.276.2 | 3 / 1 | |
| 2.275.0 | 3 / 1 | |
| 2.274.2 | 3 / 1 | |
| 2.274.1 | 3 / 1 | |
| 2.274.0 | 3 / 1 | |
| 2.273.0 | 3 / 1 | |
| 2.271.0 | 3 / 1 | |
| 2.269.1 | 3 / 1 | |
| 2.267.0 | 3 / 1 | |
| 2.266.2 | 3 / 1 | |
| 2.264.0 | 3 / 1 | |
| 2.262.1 | 3 / 1 | |
| 2.262.0 | 3 / 1 | |
| 2.260.2 | 3 / 1 | |
| 2.259.0 | 3 / 1 | |
| 2.258.0 | 3 / 1 | |
| 2.257.1 | 3 / 1 | |
| 2.257.0 | 3 / 1 | |
| 2.256.0 | 3 / 1 | |
| 2.255.0 | 3 / 1 | |
| 2.254.1 | 3 / 1 | |
| 2.253.0 | 3 / 1 | |
| 2.252.0 | 3 / 1 | |
| 2.251.1 | 3 / 1 | |
| 2.251.0 | 3 / 1 | |
| 2.250.7 | 3 / 1 | |
| 2.250.6 | 3 / 1 | |
| 2.250.5 | 3 / 1 | |
| 2.250.4 | 3 / 1 | |
| 2.250.3 | 3 / 1 | |
| 2.250.2 | 3 / 1 | |
| 2.250.1 | 3 / 1 | |
| 2.250.0 | 3 / 1 | |
| 2.248.14 | 3 / 1 | |
| 2.248.13 | 3 / 1 | |
| 2.248.12 | 3 / 1 | |
| 2.248.9 | 3 / 1 | |
| 2.248.0 | 3 / 1 | |
| 2.247.1 | 3 / 1 | |
| 2.246.0 | 3 / 1 | |
| 2.245.0 | 3 / 1 | |
| 2.244.5 | 3 / 1 | |
| 2.244.2 | 3 / 1 | |
| 2.244.1 | 3 / 1 | |
| 2.244.0 | 3 / 1 | |
| 2.242.6 | 3 / 1 | |
| 2.242.5 | 3 / 1 | |
| 2.242.4 | 3 / 1 | |
| 2.242.3 | 3 / 1 | |
| 2.242.2 | 3 / 1 | |
| 2.242.1 | 3 / 1 | |
| 2.241.0 | 3 / 1 | |
| 2.240.3 | 3 / 1 | |
| 2.239.3 | 3 / 1 | |
| 2.239.2 | 3 / 1 | |
| 2.237.1 | 3 / 1 | |
| 2.236.2 | 3 / 1 | |
| 2.235.2 | 3 / 1 | |
| 2.233.0 | 3 / 1 | |
| 2.232.0 | 3 / 1 | |
| 2.231.0 | 3 / 1 | |
| 2.229.0 | 3 / 1 | |
| 2.228.1 | 3 / 1 | |
| 2.227.1 | 3 / 1 | |
| 2.226.0 | 3 / 1 | |
| 2.225.0 | 3 / 1 | |
| 2.224.0 | 3 / 1 | |
| 2.223.0 | 3 / 1 | |
| 2.221.2 | 3 / 1 | |
| 2.221.0 | 3 / 1 | |
| 2.219.0 | 3 / 1 | |
| 2.218.3 | 3 / 1 | |
| 2.218.2 | 3 / 1 | |
| 2.218.1 | 3 / 1 | |
| 2.218.0 | 3 / 1 | |
| 2.217.0 | 3 / 1 | |
| 2.216.2 | 3 / 1 | |
| 2.216.0 | 3 / 1 | |
| 2.215.1 | 3 / 1 | |
| 2.214.1 | 3 / 1 | |
| 2.214.0 | 3 / 1 | |
| 2.213.0 | 3 / 1 | |
| 2.212.0 | 3 / 1 | |
| 2.211.0 | 3 / 1 | |
| 2.210.0 | 3 / 1 | |
| 2.208.0 | 3 / 1 | |
| 2.206.5 | 3 / 1 | |
| 2.206.4 | 3 / 1 | |
| 2.206.3 | 3 / 1 | |
| 2.206.2 | 3 / 1 | |
| 2.206.0 | 3 / 1 | |
| 2.203.0 | 3 / 1 | |
| 2.201.0 | 4 / 1 | |
| 2.199.1 | 4 / 1 | |
| 2.198.0 | 4 / 1 | |
| 2.196.0 | 4 / 1 |
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.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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.203.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.199.1
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.