@jsenv/sourcemap
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
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 3 / 0 | |
| 1.4.0 | 3 / 0 | |
| 1.3.19 | 3 / 0 | |
| 1.3.18 | 3 / 0 | |
| 1.3.17 | 3 / 0 | |
| 1.3.16 | 3 / 0 | |
| 1.3.15 | 3 / 0 | |
| 1.3.14 | 3 / 0 | |
| 1.3.13 | 3 / 0 | |
| 1.3.12 | 3 / 0 | |
| 1.3.11 | 3 / 0 | |
| 1.3.10 | 3 / 0 | |
| 1.3.9 | 3 / 0 | |
| 1.3.8 | 3 / 0 | |
| 1.3.7 | 3 / 0 | |
| 1.3.6 | 3 / 0 | |
| 1.3.5 | 3 / 0 | |
| 1.3.4 | 3 / 0 | |
| 1.3.3 | 3 / 0 | |
| 1.3.2 | 3 / 0 | |
| 1.3.1 | 3 / 0 | |
| 1.3.0 | 3 / 0 | |
| 1.2.30 | 3 / 0 | |
| 1.2.29 | 3 / 0 | |
| 1.2.28 | 3 / 0 | |
| 1.2.27 | 3 / 0 | |
| 1.2.26 | 3 / 0 | |
| 1.2.25 | 3 / 0 | |
| 1.2.24 | 3 / 0 | |
| 1.2.23 | 3 / 0 | |
| 1.2.22 | 3 / 0 | |
| 1.2.21 | 3 / 0 | |
| 1.2.20 | 3 / 0 | |
| 1.2.19 | 3 / 0 | |
| 1.2.18 | 3 / 0 | |
| 1.2.17 | 3 / 0 | |
| 1.2.16 | 3 / 0 | |
| 1.2.15 | 3 / 0 | |
| 1.2.14 | 3 / 0 | |
| 1.2.13 | 3 / 0 | |
| 1.2.12 | 3 / 0 | |
| 1.2.11 | 3 / 0 | |
| 1.2.10 | 3 / 0 | |
| 1.2.9 | 3 / 0 | |
| 1.2.8 | 3 / 0 | |
| 1.2.7 | 3 / 0 |
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.