@endo/marshal
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
Keywords
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): Known maintainer manual publish in active monorepo; dormancy reflects release cadence, not account compromise. | ai | |
| provenance | no-provenance | AI (provenance): Established @endo monorepo; provenance not historically provided across versions. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.10.0 | 7 / 0 | |
| 1.9.1 | 7 / 15 | |
| 1.9.0 | 8 / 8 | |
| 1.8.0 | 7 / 13 | |
| 1.7.1 | 6 / 13 | |
| 1.7.0 | 6 / 13 | |
| 1.6.4 | 6 / 13 | |
| 1.6.3 | 6 / 13 | |
| 1.6.2 | 6 / 7 | |
| 1.6.1 | 6 / 7 | |
| 1.6.0 | 6 / 7 | |
| 1.5.4 | 6 / 7 | |
| 1.5.3 | 6 / 7 | |
| 1.5.2 | 6 / 7 | |
| 1.5.1 | 6 / 7 | |
| 1.5.0 | 6 / 6 | |
| 1.4.1 | 6 / 6 | |
| 1.4.0 | 6 / 6 | |
| 1.3.0 | 6 / 6 | |
| 1.2.0 | 6 / 6 | |
| 1.1.0 | 4 / 6 | |
| 1.0.1 | 4 / 6 | |
| 1.0.0 | 4 / 6 |
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.