@agoric/internal
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 | large-new-source-files | AI (source-diff): Monorepo internal package expansion with first-party deps, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Consistent with added first-party @agoric/@endo functionality. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are established first-party @agoric/@endo packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with known Agoric core team; publisher has strong track record. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Used in test helper to spawn AVA child processes; passing process.env to subprocesses is standard and intentional here. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get is idiomatic in SES/Hardened JS contexts where direct property access may be intercepted; not obfuscation. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 15 / 6 | |
| 0.3.2 | 8 / 3 | |
| 0.3.1 | 8 / 3 | |
| 0.3.0 | 8 / 3 | |
| 0.2.1 | 3 / 2 | |
| 0.2.0 | 3 / 2 |
v0.3.2
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.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.