@rip-lang/stamp
Declarative host provisioning — no state file, no agent, no YAML
43
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
shreeve
Keywords
provisioningdeclarativeinfrastructureidempotentincuszfscontainersbunriprip-lang
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rip-lang | AI (phantom-deps): rip-lang is referenced in config/runtime context for this rip-lang ecosystem package; not a direct JS import by design. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 0.1.43 | 0 / 0 | |
| 0.1.42 | 1 / 0 | |
| 0.1.41 | 1 / 0 | |
| 0.1.40 | 1 / 0 | |
| 0.1.39 | 1 / 0 | |
| 0.1.38 | 1 / 0 | |
| 0.1.37 | 1 / 0 | |
| 0.1.36 | 1 / 0 | |
| 0.1.35 | 1 / 0 | |
| 0.1.34 | 1 / 0 | |
| 0.1.33 | 1 / 0 | |
| 0.1.32 | 1 / 0 | |
| 0.1.31 | 1 / 0 | |
| 0.1.30 | 1 / 0 | |
| 0.1.29 | 1 / 0 | |
| 0.1.28 | 1 / 0 | |
| 0.1.27 | 1 / 0 | |
| 0.1.26 | 1 / 0 | |
| 0.1.25 | 1 / 0 | |
| 0.1.24 | 1 / 0 | |
| 0.1.23 | 1 / 0 | |
| 0.1.22 | 1 / 0 | |
| 0.1.21 | 1 / 0 | |
| 0.1.20 | 1 / 0 | |
| 0.1.19 | 1 / 0 | |
| 0.1.18 | 1 / 0 | |
| 0.1.17 | 1 / 0 | |
| 0.1.16 | 1 / 0 | |
| 0.1.15 | 1 / 0 | |
| 0.1.14 | 1 / 0 | |
| 0.1.13 | 1 / 0 | |
| 0.1.12 | 1 / 0 | |
| 0.1.11 | 1 / 0 | |
| 0.1.10 | 1 / 0 | |
| 0.1.9 | 1 / 0 | |
| 0.1.8 | 1 / 0 | |
| 0.1.7 | 1 / 0 | |
| 0.1.6 | 1 / 0 | |
| 0.1.5 | 1 / 0 | |
| 0.1.4 | 1 / 0 | |
| 0.1.3 | 1 / 0 | |
| 0.1.2 | 1 / 0 | |
| 0.1.1 | 1 / 0 |
v0.1.43
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.