← Home

@atscript/typescript

npm Repository Homepage
37
Versions
—
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

mav-rik

Keywords

annotationsatscripttypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:moost AI (dependencies): moost is from the same moostjs org as this package; dependency is expected and consistent across versions. ai
provenance no-provenance AI (provenance): Consistent across all 76 versions; publisher pattern, not a per-version anomaly. ai

Versions (showing 37 of 37)

Version Deps Published
0.1.86 2 / 3
0.1.85 2 / 3
0.1.84 2 / 3
0.1.83 2 / 3
0.1.82 2 / 3
0.1.81 2 / 3
0.1.80 2 / 3
0.1.79 2 / 3
0.1.78 2 / 3
0.1.77 2 / 3
0.1.76 2 / 3
0.1.75 2 / 3
0.1.74 2 / 3
0.1.73 2 / 3
0.1.72 2 / 3
0.1.71 2 / 3
0.1.70 2 / 3
0.1.69 2 / 3
0.1.68 2 / 3
0.1.67 2 / 3
0.1.66 2 / 3
0.1.65 2 / 3
0.1.64 2 / 3
0.1.63 2 / 3
0.1.62 2 / 3
0.1.61 2 / 3
0.1.60 2 / 3
0.1.59 2 / 3
0.1.58 2 / 3
0.1.57 2 / 3
0.1.56 2 / 3
0.1.55 2 / 3
0.1.11 2 / 1
0.1.9 2 / 1
0.0.16 3 / 1
0.0.15 3 / 1
0.0.1 3 / 1

v0.1.86

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.85

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.84

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.83

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.82

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.81

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.80

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.79

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.16

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.15

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.